Skip to content
Fencer Intel
low 2.0

CVE-2023-3511 json

Incorrect Authorization in GitLab

published 2y ago modified 2mo ago also BIT-gitlab-2023-3511 , EUVD-2023-44170

cvss
2.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits
0
none known

Summary

An issue has been discovered in GitLab EE affecting all versions starting from 8.17 before 16.4.4, all versions starting from 16.5 before 16.5.4, all versions starting from 16.6 before 16.6.2. It was possible for auditor users to fork and submit merge requests to private projects they're not a member of.

Patch / fix

  • bitnami gitlab 16.4.4, 16.5.4, 16.6.2
  • GitLab GitLab 16.4.4, 16.5.4, 16.6.2

Is CVE-2023-3511 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-14).

Exploits and checks

  • hackerone.com https://hackerone.com/reports/2046752 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 2.0 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N
NVD 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
OSV 3.1 2.0 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami gitlab
>=8.17.0, <16.4.4
>=16.5.0, <16.5.4
>=16.6.0, <16.6.2
16.4.4
16.5.4
16.6.2

Affected products

  • GitLab GitLab

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Enhance with deb and rpm package type records.