Vulnerability in GitLab
CVE-2023-3413
An issue has been discovered in GitLab affecting all versions starting from 16.2 before 16.2.8, all versions starting from 16.3 before 16.3.5, all versions starting from 16.4 before 16.4.1. It was possible to read the source code of a project through a fork created before changing visibility to only project members.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS: 0.007 (53.1th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 53rd percentile — 53.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.006 · newest: 0.007 · change: +0.001
Affected products
- GitLab — versions 16.4, 16.4.0, 16.2
Weakness classification (CWE)
Public proof-of-concept exploits
References
- gitlab.com/gitlab-org/gitlab/-/issues/416284 (issue-tracking, Broken Link)
- hackerone.com/reports/2027967 (Permissions Required, technical-description, permissions-required, exploit)
Frequently asked questions
- What is CVE-2023-3413?
- CVE-2023-3413 is a medium-severity vulnerability in GitLab, classified under Insertion of Sensitive Information into Sent Data. CVSS score: 6.5/10. Published 2023-09-29.
- How severe is CVE-2023-3413?
- Medium severity. CVSS v3 base score is 6.5 out of 10.
- Is CVE-2023-3413 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.