Tag-name disclosure via releases API links
Published Mar 26, 2021 · Updated Aug 3, 2024
Improper authorization in GitLab allows remote authenticated users with Guest access to read tag names from private projects. The Releases API places each release tag in the _links.self URL returned to a Guest even though that role cannot view repository tags or commits. Exploitation requires Guest membership and an authenticated request to a private project's releases endpoint; the disclosed impact is limited to tag-name exposure.
Summary
What happened
Improper authorization in GitLab allows remote authenticated users with Guest access to read tag names from private projects. The Releases API places each release tag in the _links.self URL returned to a Guest even though that role cannot view repository tags or commits. Exploitation requires Guest membership and an authenticated request to a private project's releases endpoint; the disclosed impact is limited to tag-name exposure.
The record
- CVE
- CVE-2021-22172
- Published
- Mar 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-200, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=>=12.8, <13.6.6
- Affected versionversion=>=13.7.0, <13.7.6
- Affected versionversion=>=13.8.0, <13.8.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
- Guest user can see tag names reproductionfunctional · 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