Vulnerabilities · 2022 · Gitlab
CVE-2022-2095
Gitlab vulnerability
An improper access control check in GitLab CE/EE affecting all versions starting from 13.7 before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1 allows a malicious authenticated user to view a public project's Deploy Key's public fingerprint and name when that key has write permission. Note that GitLab never asks for nor stores the private key.
Affected products
Gitlab. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Gitlab runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2095.json · Vendor Advisory
- gitlab.com/gitlab-org/gitlab/-/issues/365415 · Vendor Advisory
- hackerone.com/reports/1600325 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2022-2095
- cve.org/CVERecord?id=CVE-2022-2095
More vulnerabilities in Gitlab products
CVE-2026-8716CVE-2026-6713CVE-2026-5296CVE-2026-4868CVE-2026-2601CVE-2026-1751CVE-2026-1402CVE-2026-1102All 1,290
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.