Security readout for executives and security teams
Plain-English summary
Some TeamCity versions before 2022.04.2 could accidentally print a private SSH key into a build log. If someone with access to those logs sees the key, they could use it outside TeamCity depending on what that key protects. The provided sources do not show active exploitation.
Executive priority
Treat this as a focused credential-exposure issue, not a broad remote takeover based on available evidence. Prioritize upgrade and key review where TeamCity handles deployment or source-control SSH credentials.
Technical view
CVE-2022-36321 is a CWE-532 sensitive-information-in-log issue in JetBrains TeamCity before 2022.04.2. The CVSS vector indicates network reachability, low attack complexity, high privileges required, changed scope, and low confidentiality impact, with no integrity or availability impact recorded.
Likely exposure
Exposure is most likely on TeamCity deployments before 2022.04.2 that use private SSH keys in build workflows and allow users or integrations to read build logs.
Exploitation context
The source bundle does not list CISA KEV status or cite active exploitation. Practical impact depends on whether private SSH keys were logged, who could read those logs, and what systems those keys access.
Researcher notes
Evidence is sparse: the public description says private SSH keys could be written to build logs “in some cases,” but does not define exact trigger conditions. Avoid assuming exploitability beyond privileged log access and affected TeamCity versions before 2022.04.2.
Mitigation direction
- Upgrade TeamCity to 2022.04.2 or later, following JetBrains guidance.
- Restrict build log access to users with a clear operational need.
- Rotate any SSH private keys suspected of appearing in build logs.
- Review JetBrains fixed-issue guidance for version-specific remediation details.
Validation and detection
- Inventory TeamCity instances and confirm whether any are before 2022.04.2.
- Identify builds that used private SSH keys before remediation.
- Review accessible build logs for accidental private key exposure.
- Confirm exposed or suspected keys were revoked and replaced.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-532: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-36321 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N2.31.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.jetbrains.com/privacy-security/issues-fixed/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information into Log File
Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.