Persistent account access via invalidated tokens
Published Jul 22, 2024 · Updated Aug 2, 2024
Insufficient token expiration in JetBrains TeamCity before 2024.07 allows remote attackers to retain access with deleted or expired tokens. The access-token validation path continues accepting a token after deletion or expiration; JetBrains has not identified the responsible function. Exploitation requires possession of a formerly valid token and preserves its associated account permissions after the intended authorization ends.
Summary
What happened
Insufficient token expiration in JetBrains TeamCity before 2024.07 allows remote attackers to retain access with deleted or expired tokens. The access-token validation path continues accepting a token after deletion or expiration; JetBrains has not identified the responsible function. Exploitation requires possession of a formerly valid token and preserves its associated account permissions after the intended authorization ends.
The record
- CVE
- CVE-2024-41827
- Published
- Jul 22, 2024
- Updated
- Aug 2, 2024
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-613, T1078
- Attack vector
- network
- Privileges
- unauthenticated
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?
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