dbcve.org
TeamcityApplication · Jetbrains

CVE-2022-36322

HIGH · 8.8 CVSS v3.1 Published 2022-07-20
Fix available
A fix is available. Upgrade to 2022.04.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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.2 build parameter injection was possible

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 · moderate confidence

In JetBrains TeamCity before version 2022.04.2, a build parameter injection vulnerability existed that could allow authenticated users (or potentially unauthenticated attackers depending on configuration) to inject malicious content into build parameters, potentially leading to command execution, credential theft, or manipulation of build processes.

MitigationUpgrade TeamCity to version 2022.04.2 or later. If immediate patching is not possible, restrict build configuration permissions to trusted users only and audit existing build configurations for suspicious parameter values.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 installed TeamCity version
    Navigate to Administration > Global Settings in the TeamCity web UI, or check the TeamCity server logs at <TeamCity data directory>/logs/teamcity-server.log for the version string on startup
    Affected if The version number is lower than 2022.04.2 (for example, 2022.04.1, 2022.03.x, earlier versions)
  2. Verify build configuration permissions
    Go to Administration > Users and Administration > User Groups to review which users have permissions to edit build configurations and parameters
    Affected if Users other than trusted administrators have permission to modify build configurations or build parameters
  3. Inspect build parameters for suspicious values
    Review existing build configurations at Projects > <Project Name> > Build Configurations > <Config Name> > Parameters tab; look for parameters containing commands, scripts, or paths that could indicate injection attempts
    Affected if Any build parameter values contain unexpected commands, script execution syntax, or reference sensitive environment variables
  4. Check for unauthenticated or guest access
    Navigate to Administration > Authentication Settings to verify if anonymous access or guest login is enabled
    Affected if Anonymous access or guest user login is enabled, allowing unauthenticated users to potentially interact with build parameters

You are affected if your TeamCity version is earlier than 2022.04.2 AND either build parameter modification permissions exist for untrusted users or anonymous/guest access is enabled.

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.2 or later
Fixed in 2022.04.2
Interim mitigation

Upgrade TeamCity to version 2022.04.2 or later. If immediate patching is not possible, restrict build configuration permissions to trusted users only and audit existing build configurations for suspicious parameter values.

Recommended fix High confidence

2022.04.2 or later

  1. Back up your TeamCity server data and configuration before proceeding with the upgrade
  2. Download TeamCity version 2022.04.2 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. Stop the TeamCity server service
  4. Run the installer for the new version, following the on-screen prompts
  5. Start the TeamCity server service after installation completes
  6. Verify the upgrade was successful by logging into the TeamCity web interface and checking the build configuration
Caveat Review TeamCity release notes for any migration notes between your current version and 2022.04.2; minor version upgrades typically have minimal breaking changes

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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