Security readout for executives and security teams
Plain-English summary
CVE-2022-4343 is a GitLab EE information disclosure flaw. A project member could leak credentials stored in a site profile. It is not described as unauthenticated or actively exploited in the provided sources, but exposed credentials can create downstream business risk if reused or privileged.
Executive priority
Treat as a scheduled security maintenance item with credential-review urgency. Escalate priority if affected projects contain production, cloud, deployment, or shared credentials, because the vulnerability’s direct impact is disclosure rather than service disruption.
Technical view
GitLab EE versions from 13.12 before 16.1.5, 16.2 before 16.2.5, and 16.3 before 16.3.1 are affected. The CVSS 3.1 score is 5.0, with low attack complexity, low privileges required, no user interaction, changed scope, and low confidentiality impact.
Likely exposure
Exposure is most likely where affected GitLab EE versions are in use and project members can access projects with credentials stored in site profiles. Systems without affected versions or without such stored credentials appear less exposed based on the bundle.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation evidence. A public HackerOne report is referenced for technical and permission context, but the safe conclusion is that exploitation requires project-member privileges.
Researcher notes
The core evidence is version-range and access-condition based. The bundle does not provide detailed vulnerable code paths, exact credential type, or post-fix behavioral details. Avoid assuming unauthenticated access, broader GitLab editions, or confirmed exploitation without additional vendor evidence.
Mitigation direction
- Upgrade affected GitLab EE deployments to 16.1.5, 16.2.5, 16.3.1, or later supported releases.
- Review vendor guidance for any additional GitLab-specific remediation notes.
- Audit site profile credentials stored in affected projects.
- Rotate exposed or potentially exposed credentials, prioritizing privileged and reused secrets.
- Reduce project membership to users with a current business need.
Validation and detection
- Inventory GitLab EE versions across hosted and self-managed environments.
- Check whether any instance falls in the affected version ranges.
- Identify projects with credentials stored in site profiles.
- Review project member access for affected projects.
- Confirm remediation by verifying upgraded GitLab versions after maintenance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-4343 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N3.11.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #385124CVE reference · issue-tracking
- HackerOne Bug Bounty Report #1767797CVE reference · technical-description, exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.