Access-token disclosure through GRPC exception logging
Published Apr 15, 2023 · Updated Feb 6, 2025
Information disclosure in affected GitLab Community and Enterprise Edition releases allows attackers to obtain sensitive access-token data. The exception-reporting path records GRPC::Unknown exception contents, including sensitive access tokens, in Sentry logs rather than excluding token data. Exposure requires the affected instance to send these exceptions to Sentry and access to the resulting log events; the disclosed consequence is token disclosure without reported data modification or service interruption.
Summary
What happened
Information disclosure in affected GitLab Community and Enterprise Edition releases allows attackers to obtain sensitive access-token data. The exception-reporting path records GRPC::Unknown exception contents, including sensitive access tokens, in Sentry logs rather than excluding token data. Exposure requires the affected instance to send these exceptions to Sentry and access to the resulting log events; the disclosed consequence is token disclosure without reported data modification or service interruption.
The record
- CVE
- CVE-2018-17453
- Published
- Apr 15, 2023
- Updated
- Feb 6, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1552
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2023CVE publishedPublication date reported by the CVE source.
- Feb 6, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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