Authenticated disclosure through build feature authorization
Published May 29, 2024 · Updated Aug 2, 2024
Incorrect authorization in JetBrains TeamCity allows remote authenticated users to read protected data through two build features. JetBrains identifies the Pull Requests and Commit Status Publisher build features but has not disclosed the specific missing authorization check or data exposed. A low-privileged account and HTTP(S) access to an affected on-premises server are required; the published impact is limited to confidentiality.
Summary
What happened
Incorrect authorization in JetBrains TeamCity allows remote authenticated users to read protected data through two build features. JetBrains identifies the Pull Requests and Commit Status Publisher build features but has not disclosed the specific missing authorization check or data exposed. A low-privileged account and HTTP(S) access to an affected on-premises server are required; the published impact is limited to confidentiality.
The record
- CVE
- CVE-2024-36364
- Published
- May 29, 2024
- Updated
- Aug 2, 2024
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
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 <2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5
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