Access-token disclosure via logged API query parameters
Published Aug 8, 2024 · Updated Aug 29, 2024
Information exposure in affected GitLab CE/EE releases allows remote authenticated users to place access tokens in server logs via API requests. A specifically formed API request retains access-token data in query parameters that GitLab records in its logs; the endpoint and logging path are undisclosed. Administrative privileges are required, and the reported consequence is token disclosure without integrity or availability impact.
Summary
What happened
Information exposure in affected GitLab CE/EE releases allows remote authenticated users to place access tokens in server logs via API requests. A specifically formed API request retains access-token data in query parameters that GitLab records in its logs; the endpoint and logging path are undisclosed. Administrative privileges are required, and the reported consequence is token disclosure without integrity or availability impact.
The record
- CVE
- CVE-2024-7554
- Published
- Aug 8, 2024
- Updated
- Aug 29, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-200, T1552.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Aug 8, 2024CVE publishedPublication date reported by the CVE source.
- Aug 29, 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.9 <17.0.6
- Affected versionversion=17.1 <17.1.4
- Affected versionversion=17.2 <17.2.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