dbcve.org
TeamcityApplication · Jetbrains

CVE-2022-48342

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-23
Fix available
A fix is available. Upgrade to 2022.10.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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.10.2 jVMTI was enabled by default on agents.

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 before version 2022.10.2, the Java Virtual Machine Tool Interface (jVMTI) was enabled by default on all build agents. jVMTI is a native interface that provides deep inspection and control capabilities over the JVM, allowing examination of thread states, heap memory, and potentially enabling code execution or manipulation of running Java applications. This default configuration exposed a critical attack surface where compromised agents or malicious builds could leverage jVMTI for privilege escalation, credential theft, or arbitrary code execution within agent contexts.

MitigationUpgrade TeamCity server and all agents to version 2022.10.2 or later, which disables jVMTI by default. If immediate upgrading is not feasible, explicitly disable jVMTI in agent configuration files and review agent access controls.

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.10.2

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Check TeamCity server version
    Access the TeamCity server administration UI, go to 'Administration' > 'Server Administration' > 'Server Information', or query the server via API endpoint /app/rest/server/version to retrieve the installed version number
    Affected if Version is lower than 2022.10.2
  2. Check build agent version
    In TeamCity web UI, navigate to 'Agents' > 'Agent' > 'Agent Details' to see the agent version, or review agent logs on startup which display the TeamCity agent version
    Affected if Agent version is lower than 2022.10.2 matching affected server versions
  3. Inspect jVMTI configuration in agent config file
    Locate the build agent configuration file (commonly named buildAgent.properties or within conf directory under the agent installation root). Search for properties containing 'jvmti' or 'jvmToolInterface'
    Affected if Property 'teamcity.jvmti.agent.enable=true' is present, or jVMTI is not explicitly set to false (in affected versions, jVMTI is enabled by default)
  4. Verify jVMTI status via agent parameters
    In TeamCity web UI under 'Agents' > 'Agent Name' > 'Parameters', review system and environment variables for jVMTI-related entries such as 'agent.jvmti.access' or similar jVMTI enable flags
    Affected if jVMTI-related parameters show the feature as enabled or not explicitly disabled

You are affected if your TeamCity installation (server or any agent) is version 2022.10.1 or earlier AND jVMTI remains enabled in the agent configuration (the default state in vulnerable versions).

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.10.2 or later
Fixed in 2022.10.2
Interim mitigation

Upgrade TeamCity server and all agents to version 2022.10.2 or later, which disables jVMTI by default. If immediate upgrading is not feasible, explicitly disable jVMTI in agent configuration files and review agent access controls.

Recommended fix High confidence

TeamCity 2022.10.2 or later

  1. Back up your TeamCity database and configuration files
  2. Stop all TeamCity servers and agents
  3. Download TeamCity 2022.10.2 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
  4. Follow JetBrains official upgrade documentation to install the new version
  5. Start the TeamCity server and agents after upgrade
  6. Verify the upgrade was successful by checking the TeamCity version in the administration UI
Caveat Review JetBrains release notes for this version for any configuration or feature changes that may affect your setup

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-48342 — 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-48342 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