Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Gitlab | Gitlab | >= 13.7.0, < 15.0.5 |
Related Weaknesses (CWE)
References
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2095.jsonVendor Advisory
- https://gitlab.com/gitlab-org/gitlab/-/issues/365415Broken LinkVendor Advisory
- https://hackerone.com/reports/1600325Permissions RequiredThird Party Advisory
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2095.jsonVendor Advisory
- https://gitlab.com/gitlab-org/gitlab/-/issues/365415Broken LinkVendor Advisory
- https://hackerone.com/reports/1600325Permissions RequiredThird Party Advisory
FAQ
What is CVE-2022-2095?
CVE-2022-2095 is a vulnerability with a CVSS score of 4.3 (MEDIUM). 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 a...
How severe is CVE-2022-2095?
CVE-2022-2095 has been rated MEDIUM with a CVSS base score of 4.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-2095?
Check the references section above for vendor advisories and patch information. Affected products include: Gitlab Gitlab.