Authenticated GitHub token disclosure via incorrect authorization
Published Feb 3, 2021 · Updated Aug 3, 2024
Incorrect authorization in JetBrains TeamCity before 2020.2.1 allows remote authenticated users to obtain another user's GitHub access token. JetBrains has not disclosed the affected endpoint or the missing authorization operation that exposes the token. An authenticated TeamCity account is required, and the consequence is limited to disclosure and potential reuse of another user's GitHub credential.
Summary
What happened
Incorrect authorization in JetBrains TeamCity before 2020.2.1 allows remote authenticated users to obtain another user's GitHub access token. JetBrains has not disclosed the affected endpoint or the missing authorization operation that exposes the token. An authenticated TeamCity account is required, and the consequence is limited to disclosure and potential reuse of another user's GitHub credential.
The record
- CVE
- CVE-2021-25774
- Published
- Feb 3, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 3, 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?
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.
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