Private SSH key disclosure via build logging
Published Jul 20, 2022 · Updated Aug 3, 2024
Sensitive information exposure in JetBrains TeamCity before 2022.04.2 allows remote authenticated users to read private SSH keys in build logs. In affected cases, the server records an uploaded SSH private key in retained build output instead of keeping the credential out of the log. The vulnerable workflow requires privileged access to configure or inspect builds, and the reported consequence is disclosure of the logged key without integrity or availability impact.
Summary
What happened
Sensitive information exposure in JetBrains TeamCity before 2022.04.2 allows remote authenticated users to read private SSH keys in build logs. In affected cases, the server records an uploaded SSH private key in retained build output instead of keeping the credential out of the log. The vulnerable workflow requires privileged access to configure or inspect builds, and the reported consequence is disclosure of the logged key without integrity or availability impact.
The record
- CVE
- CVE-2022-36321
- Published
- Jul 20, 2022
- Updated
- Aug 3, 2024
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-532, T1552.004
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jul 20, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=2022.04.2 <2022.04.2
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