High [CVE-2023-4379] Incorrect Authorization in GitLab
This high-severity GitLab advisory covers CVE-2023-4379 affecting GitLab.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published
Android app · Google Play
Monitor future GitLab CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
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.
- GitLab 15.3 before 16.2.8
- GitLab 16.3 before 16.3.5
- GitLab 16.4 before 16.4.1
Official advisory · high-confidence parse· fetched 5 days ago·verify at source
- 16.2.8
- 16.3.5
- 16.4.1
Official advisory · high-confidence parse· fetched 5 days ago·verify at source
Mitigation
Upgrade to a fixed release: 16.2.8, 16.3.5, 16.4.1. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 5 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.