Release-name disclosure via unchecked tag rendering
Published Jan 24, 2023 · Updated Apr 2, 2025
Improper access control in GitLab 11.3 through 15.4.5, 15.5 through 15.5.4, and 15.6.0 allows remote attackers to read release names. The server-rendered tag partial displays the release associated with each public repository tag without checking whether the requester can read releases. A public project with releases limited to project members is required, and exposure is limited to release names rather than release contents.
Summary
What happened
Improper access control in GitLab 11.3 through 15.4.5, 15.5 through 15.5.4, and 15.6.0 allows remote attackers to read release names. The server-rendered tag partial displays the release associated with each public repository tag without checking whether the requester can read releases. A public project with releases limited to project members is required, and exposure is limited to release names rather than release contents.
The record
- CVE
- CVE-2022-3482
- Published
- Jan 24, 2023
- Updated
- Apr 2, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 2023CVE publishedPublication date reported by the CVE source.
- Apr 2, 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=>=11.3, <15.4.6
- Affected versionversion=>=15.5, <15.5.5
- Affected versionversion=>=15.6, <15.6.1
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.
Public exploit references
- Public tag-page release-name disclosure reproductionproof of concept · demonstrated
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