Credential disclosure via build-log credential insertion
Published Apr 25, 2025 · Updated Apr 25, 2025
Sensitive-data logging in JetBrains TeamCity before 2025.03.1 allows remote authenticated users to read base64-encoded credentials in build logs. The published record identifies credential insertion in build-log output but does not disclose the responsible function or input path. Access to affected build logs is required, and the reported consequence is credential disclosure without data modification or service interruption.
Summary
What happened
Sensitive-data logging in JetBrains TeamCity before 2025.03.1 allows remote authenticated users to read base64-encoded credentials in build logs. The published record identifies credential insertion in build-log output but does not disclose the responsible function or input path. Access to affected build logs is required, and the reported consequence is credential disclosure without data modification or service interruption.
The record
- CVE
- CVE-2025-46432
- Published
- Apr 25, 2025
- Updated
- Apr 25, 2025
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 25, 2025CVE publishedPublication date reported by the CVE source.
- Apr 25, 2025Record 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 <2025.03.1
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