CVE-2022-4343

Public Exploit
Exposure of Sensitive Information to an Unauthorized Actor in GitLab

Description

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.

Remediation

Solution:

  • Upgrade to versions 16.1.5, 16.2.5, 16.3.1 or above.

Category

5.0
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.03%
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/385124 issue tracking broken link
https://hackerone.com/reports/1767797 broken link exploit permissions required technical description

Frequently Asked Questions

What is the severity of CVE-2022-4343?
CVE-2022-4343 has been scored as a medium severity vulnerability.
How to fix CVE-2022-4343?
To fix CVE-2022-4343: Upgrade to versions 16.1.5, 16.2.5, 16.3.1 or above.
Is CVE-2022-4343 being actively exploited in the wild?
It is possible that CVE-2022-4343 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-4343?
CVE-2022-4343 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.