Credential disclosure via Base64 build-log encoding
Published Mar 27, 2025 · Updated Mar 27, 2025
Sensitive information exposure in JetBrains TeamCity before 2025.03 allows remote authenticated users to read a password from a build log. The affected logging path writes a Base64 encoding of a password to build output; JetBrains has not disclosed the responsible component or operation. Access requires permission to view the affected build log, and the bounded consequence is disclosure of the encoded credential rather than code execution or data modification.
Summary
What happened
Sensitive information exposure in JetBrains TeamCity before 2025.03 allows remote authenticated users to read a password from a build log. The affected logging path writes a Base64 encoding of a password to build output; JetBrains has not disclosed the responsible component or operation. Access requires permission to view the affected build log, and the bounded consequence is disclosure of the encoded credential rather than code execution or data modification.
The record
- CVE
- CVE-2025-31139
- Published
- Mar 27, 2025
- Updated
- Mar 27, 2025
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2025CVE publishedPublication date reported by the CVE source.
- Mar 27, 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
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