CVE-2022-36321 json
In JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases
published 4y ago modified 4mo ago also EUVD-2022-39037
- cvss
- 4.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
In JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases
Patch / fix
- jetbrains teamcity 2022.04.2
Is CVE-2022-36321 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.89% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- JetBrains TeamCity
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
References
-
jetbrains.com
/privacy-security/issues-fixed/
vendor-advisory
Sources
- CVE List CVE-2022-36321
- NVD CVE-2022-36321
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.