CVE-2022-36321
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn JetBrains TeamCity versions before 2022.04.2, private SSH keys could inadvertently be written to build logs due to improper handling of SSH key data during build processes. This exposes sensitive credential material through log files that may be accessible to unauthorized users with log access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2022.04.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check TeamCity versionAccess the TeamCity administration interface and navigate to 'About' or check the version via the server health report. Alternatively, check the TeamCity server logs or the version displayed on the login page.Affected if The installed version is below 2022.04.2 (for example, 2022.04.1, 2022.03.x, or earlier)
-
Identify build configurations using SSH keysReview your build configurations in TeamCity to determine if any use SSH keys as authentication credentials. Check the 'SSH Key' or 'SSH Auth' build feature settings, or look for parameter types referencing private keys.Affected if At least one build configuration uses SSH key authentication for clone operations or remote commands
-
Examine build logs for SSH key materialReview recent build logs, especially from builds that clone repositories via SSH or execute remote SSH commands. Search for patterns resembling SSH private key headers (-----BEGIN OPENSSH PRIVATE KEY-----, -----BEGIN RSA PRIVATE KEY-----) or key-like strings in the log output.Affected if Build logs contain any lines resembling SSH private key material
A user is affected if their TeamCity version is below 2022.04.2, they have builds using SSH keys, and their build logs contain exposed SSH private key data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2022.04.2
Upgrade TeamCity to version 2022.04.2 or later to remediate. Additionally, audit existing build logs for exposed SSH keys and rotate any keys that may have been disclosed.
2022.04.2
- Back up your current TeamCity data and configuration before upgrading
- Download TeamCity version 2022.04.2 or later from the official JetBrains website
- Stop the TeamCity server and agents
- Install the new version following the standard TeamCity upgrade procedure
- Start the TeamCity server and verify the upgrade was successful
- Verify that SSH keys are no longer being written to build logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36321 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data