Unauthenticated service interruption via incorrect auth tokens
Published May 29, 2024 · Updated Aug 2, 2024
Resource exhaustion in JetBrains TeamCity before 2024.03.2 allows remote attackers to interrupt the server with incorrect auth tokens. JetBrains has not disclosed which token-processing component allocates resources without adequate limits or how malformed tokens trigger exhaustion. Network access to the TeamCity server is sufficient; the documented effect is service interruption without confidentiality or integrity impact.
Summary
What happened
Resource exhaustion in JetBrains TeamCity before 2024.03.2 allows remote attackers to interrupt the server with incorrect auth tokens. JetBrains has not disclosed which token-processing component allocates resources without adequate limits or how malformed tokens trigger exhaustion. Network access to the TeamCity server is sufficient; the documented effect is service interruption without confidentiality or integrity impact.
The record
- CVE
- CVE-2024-36378
- Published
- May 29, 2024
- Updated
- Aug 2, 2024
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 29, 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.03.2
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.
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