Unauthenticated release-description disclosure via missing access check
Published Mar 9, 2023 · Updated Feb 28, 2025
Information disclosure in GitLab allows remote attackers to read project-member-only release descriptions through the Releases API. The API returns the description field without enforcing the project setting that restricts release visibility to project members. No authentication or user interaction is required on GitLab 15.5 through 15.7.7, 15.8 through 15.8.3, or 15.9 through 15.9.1; impact is limited to disclosure of release text.
Summary
What happened
Information disclosure in GitLab allows remote attackers to read project-member-only release descriptions through the Releases API. The API returns the description field without enforcing the project setting that restricts release visibility to project members. No authentication or user interaction is required on GitLab 15.5 through 15.7.7, 15.8 through 15.8.3, or 15.9 through 15.9.1; impact is limited to disclosure of release text.
The record
- CVE
- CVE-2023-0223
- Published
- Mar 9, 2023
- Updated
- Feb 28, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 9, 2023CVE publishedPublication date reported by the CVE source.
- Feb 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>=15.5, <15.7.8
- Affected versionversion=>=15.8, <15.8.4
- Affected versionversion=>=15.9, <15.9.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo