Auth bypass in Gitlab
CVE-2022-2095
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.
Vulnerability class: Broken Access Control
EPSS: 0.008 (51.4th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
Affected products
- Gitlab — versions >=15.1, <15.1.4, >=15.2, <15.2.1, >=13.7, <15.0.5
Weakness classification (CWE)
References
- cve@gitlab.com (x_refsource_MISC, Broken Link, Vendor Advisory)
- cve@gitlab.com (Permissions Required, Third Party Advisory, x_refsource_MISC)
- cve@gitlab.com (x_refsource_CONFIRM, Vendor Advisory)
Frequently asked questions
- What is CVE-2022-2095?
- CVE-2022-2095 is a medium-severity vulnerability in Gitlab, classified under Incorrect Authorization. CVSS score: 4.3/10. Published 2022-08-05.
- How severe is CVE-2022-2095?
- Medium severity. CVSS v3 base score is 4.3 out of 10.