OAuth code theft via Space application callback
Published Jul 22, 2024 · Updated Aug 2, 2024
Incorrect OAuth authentication in JetBrains TeamCity before 2024.07 allows remote authenticated users to steal a JetBrains Space OAuth code. The Space Application connection processes an authorization-code callback, but JetBrains has not published the exact validation error that permits diversion. Exploitation requires a configured Space connection, low-privileged access, and victim interaction; the reported consequence is OAuth-code disclosure.
Summary
What happened
Incorrect OAuth authentication in JetBrains TeamCity before 2024.07 allows remote authenticated users to steal a JetBrains Space OAuth code. The Space Application connection processes an authorization-code callback, but JetBrains has not published the exact validation error that permits diversion. Exploitation requires a configured Space connection, low-privileged access, and victim interaction; the reported consequence is OAuth-code disclosure.
The record
- CVE
- CVE-2024-41829
- Published
- Jul 22, 2024
- Updated
- Aug 2, 2024
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-287, CWE-303
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 22, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=0 <2024.07
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