Agent metadata disclosure via overbroad developer permission
Published Dec 20, 2024 · Updated Dec 20, 2024
Improper access control in JetBrains TeamCity before 2024.12 allows remote authenticated users to view unauthorized agent details. The default Project Developer role used the server-wide View agent details permission instead of restricting visibility to agents in the user's project pools. A low-privileged project developer can therefore inspect metadata for build agents assigned outside authorized projects; JetBrains has not disclosed the exact fields exposed.
Summary
What happened
Improper access control in JetBrains TeamCity before 2024.12 allows remote authenticated users to view unauthorized agent details. The default Project Developer role used the server-wide View agent details permission instead of restricting visibility to agents in the user's project pools. A low-privileged project developer can therefore inspect metadata for build agents assigned outside authorized projects; JetBrains has not disclosed the exact fields exposed.
The record
- CVE
- CVE-2024-56348
- Published
- Dec 20, 2024
- Updated
- Dec 20, 2024
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 20, 2024CVE publishedPublication date reported by the CVE source.
- Dec 20, 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.12
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