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
Published · last modified .
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.
EPSS exploit prediction
EPSS: 0.009 (57.5th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 58th percentile — 57.5% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.009 · newest: 0.009 · change: 0.000
Affected products
- GitLab — versions >=15.1, <15.1.4, >=15.2, <15.2.1, >=13.7, <15.0.5
Weakness classification (CWE)
References
- gitlab.com/gitlab-org/gitlab/-/issues/365415 (Broken Link, Vendor Advisory)
- hackerone.com/reports/1600325 (Permissions Required, Third Party Advisory)
- gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2095.json (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.