CVE-2023-3949 Insertion of Sensitive Information Into Sent Data in GitLab
Unauthorized users can view restricted release descriptions on public projects via an atom endpoint when access is limited to members.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-3949?
CVE-2023-3949 is a medium-severity vulnerability in Gitlab Gitlab, published on 1 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
An issue has been discovered in GitLab affecting all versions starting from 11.3 before 16.4.3, all versions starting from 16.5 before 16.5.3, all versions starting from 16.6 before 16.6.1. It was possible for unauthorized users to view a public projects' release descriptions via an atom endpoint when release access on the public was set to only project members.
Weakness: CWE-201
Which versions are affected by CVE-2023-3949?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 11.3.0 | 16.4.3, 16.5.3, 16.6.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2023-3949?
Upgrade gitlab to a fixed version for your release line: 16.4.3, 16.5.3 or 16.6.1.
Is CVE-2023-3949 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3949 exists.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2023-3949, GHSA-c3hq-3p4c-ch2w.