🛡️ CVE-2022-4343 — gitlab
Description
Exposure of Sensitive Information to an Unauthorized Actor in GitLab
An issue has been discovered in GitLab EE affecting all versions starting from 13.12 before 16.1.5, all versions starting from 16.2 before 16.2.5, all versions starting from 16.3 before 16.3.1 in which a project member can leak credentials stored in site profile.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality low, integrity none, availability none.
Weakness class
CVE-2022-4343 is classified as CWE-200: Exposure of Sensitive Information. Information that should stay internal is disclosed to someone who is not authorised to see it.
Affected software
CVE-2022-4343 is recorded against 1 package.
- gitlab
Timeline and source
Published on 6 March 2024 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| gitlab | — | — |
References
Similar Threats
- High CVE-2020-10073
- Critical CVE-2020-10074
- Medium CVE-2020-10075
- Medium CVE-2020-10076
- Critical CVE-2020-10077
More CVE 2022 advisories
Browse all of CVE 2022 in the advisory index.
Vulnerability Monitoring
Track new vulnerabilities in gitlab
CVE-2022-4343 is rated CVSS 5.0 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.