Skip to content
Fencer Intel
high 8.1

CVE-2023-4379 json

Incorrect Authorization in GitLab

published 3y ago modified 13d ago also BIT-gitlab-2023-4379 , EUVD-2023-54243

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

Summary

An issue has been discovered in GitLab EE affecting all versions starting from 15.3 prior to 16.2.8, 16.3 prior to 16.3.5, and 16.4 prior to 16.4.1. Code owner approval was not removed from merge requests when the target branch was updated.

Patch / fix

  • bitnami gitlab 16.2.8, 16.3.5, 16.4.1
  • GitLab GitLab 16.2.8, 16.3.5, 16.4.1

Is CVE-2023-4379 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

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami gitlab
>=15.3.0, <16.2.8
>=16.3.0, <16.3.5
>=16.4.0, <16.4.1
16.2.8
16.3.5
16.4.1

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.