dbcve.org
TeamcityApplication · Jetbrains

CVE-2022-38133

MEDIUM · 5.3 CVSS v3.1 Published 2022-08-10
Fix available
A fix is available. Upgrade to 2022.04.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server 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 confidence

In JetBrains TeamCity versions prior to 2022.04.3, private SSH keys used for authentication were inadvertently written to server log files due to improper handling during SSH key operations. This exposed sensitive credential data to anyone with access to the TeamCity server logs.

MitigationUpgrade TeamCity to version 2022.04.3 or later. Additionally, review server log files for any unauthorized access and consider rotating SSH keys that may have been exposed.

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
TeamcityApplication
Affected:< 2022.04.3

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify TeamCity version
    Check the TeamCity server version by navigating to the Administration > Troubleshooting section in the web UI, or locate the version in the logs/teamcity-server.log file
    Affected if Version is earlier than 2022.04.3 (e.g., 2022.04.2, 2022.04.1, 2022.04, 2022.03.x, etc.)
  2. Confirm SSH key authentication is configured
    Navigate to Administration > SSH Keys in the TeamCity web interface, or inspect project VCS settings for SSH-based repository connections
    Affected if SSH keys are configured or used for VCS authentication, Git SSH URLs, or SSH-based build features
  3. Search logs for SSH private key material
    Grep through TeamCity server logs (typically in <TeamCity_home>/logs/teamcity-server.log and teamcity-nio.log) using pattern matching for private key markers such as '-----BEGIN RSA PRIVATE KEY-----', '-----BEGIN OPENSSH PRIVATE KEY-----', or '-----BEGIN DSA PRIVATE KEY-----'
    Affected if Log files contain any PEM-formatted private key headers or base64-encoded key data that resembles SSH private keys
  4. Check log file access controls
    Review file system permissions on the TeamCity logs directory and verify who has read access to teamcity-server.log and related log files
    Affected if Log files are accessible to unauthorized users or have overly permissive ACLs (e.g., world-readable)
  5. Review recent log file access history
    Check operating system audit logs or TeamCity access logs for any unusual read access to the logs directory by unexpected users or from unexpected IP addresses
    Affected if Log files containing potential SSH keys have been accessed by users other than administrators

Environment is affected if TeamCity version is before 2022.04.3 AND SSH key authentication is configured AND private key material may exist in accessible log files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2022.04.3 or later
Fixed in 2022.04.3
Interim mitigation

Upgrade TeamCity to version 2022.04.3 or later. Additionally, review server log files for any unauthorized access and consider rotating SSH keys that may have been exposed.

Recommended fix High confidence

2022.04.3 or later

  1. 1. Back up the TeamCity data directory and database before upgrading
  2. 2. Download TeamCity 2022.04.3 or a later stable version from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Stop the running TeamCity server service
  4. 4. Run the installer or extract the new version to replace the existing installation
  5. 5. Start the TeamCity server and verify it is running correctly
  6. 6. Review server logs to confirm the SSH key is no longer being written to log files
Caveat Review JetBrains release notes for 2022.04.x for any migration or compatibility notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38133 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38133 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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