Password disclosure via special-character masking failure
Published Nov 3, 2022 · Updated May 2, 2025
Sensitive information exposure in JetBrains TeamCity before 2022.10 allows remote authenticated users to read password parameters in build logs. The build-log masking logic fails to replace password parameter values containing special characters, leaving the original secret in logged command output. A user must be able to access an affected build log, and the consequence is limited to disclosure of password-parameter contents recorded there.
Summary
What happened
Sensitive information exposure in JetBrains TeamCity before 2022.10 allows remote authenticated users to read password parameters in build logs. The build-log masking logic fails to replace password parameter values containing special characters, leaving the original secret in logged command output. A user must be able to access an affected build log, and the consequence is limited to disclosure of password-parameter contents recorded there.
The record
- CVE
- CVE-2022-44624
- Published
- Nov 3, 2022
- Updated
- May 2, 2025
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-532, CAPEC-215, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 3, 2022CVE publishedPublication date reported by the CVE source.
- May 2, 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=2022.10 <2022.10
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