Password disclosure via unmasked dependency parameters
Published May 31, 2023 · Updated Jan 9, 2025
Sensitive-data exposure in JetBrains TeamCity before 2023.05 allows remote authenticated users to read dependency passwords from build logs. When a build consumes a password-type parameter from a build dependency, an undisclosed masking path writes the secret into the build log instead of redacting it. A low-privileged account must be able to trigger the affected dependency flow and access the resulting log; the reported consequence is limited to disclosure of those parameter values.
Summary
What happened
Sensitive-data exposure in JetBrains TeamCity before 2023.05 allows remote authenticated users to read dependency passwords from build logs. When a build consumes a password-type parameter from a build dependency, an undisclosed masking path writes the secret into the build log instead of redacting it. A low-privileged account must be able to trigger the affected dependency flow and access the resulting log; the reported consequence is limited to disclosure of those parameter values.
The record
- CVE
- CVE-2023-34223
- Published
- May 31, 2023
- Updated
- Jan 9, 2025
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 31, 2023CVE publishedPublication date reported by the CVE source.
- Jan 9, 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 <2023.05
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