Unauthenticated token-name disclosure via GraphQL authorization gap
Published Dec 13, 2021 · Updated Aug 4, 2024
Improper access control in GitLab GraphQL API before 14.3.6, 14.4.4, or 14.5.2 allows remote attackers to view project access-token names. The GraphQL user and project resolvers expose bot-account names derived from project access tokens without enforcing authorization for arbitrary projects. The request is unauthenticated and read-only, so the consequence is disclosure of token naming metadata rather than token use or configuration changes.
Summary
What happened
Improper access control in GitLab GraphQL API before 14.3.6, 14.4.4, or 14.5.2 allows remote attackers to view project access-token names. The GraphQL user and project resolvers expose bot-account names derived from project access tokens without enforcing authorization for arbitrary projects. The request is unauthenticated and read-only, so the consequence is disclosure of token naming metadata rather than token use or configuration changes.
The record
- CVE
- CVE-2021-39915
- Published
- Dec 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-668, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=>=13.0, <14.3.6
- Affected versionversion=>=14.4, <14.4.4
- Affected versionversion=>=14.5, <14.5.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.
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