dbcve.org
TeamcityApplication · Jetbrains

CVE-2022-44624

HIGH · 7.5 CVSS v3.1 Published 2022-11-03
Fix available
A fix is available. Upgrade to 2022.10 or later.
See remediation →
84/100
Remediation priority · High
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 version before 2022.10, Password parameters could be exposed in the build log if they contained special characters

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 before 2022.10, password parameters containing special characters were incorrectly logged to build output. When special characters were present in password-type build parameters, the values were not properly sanitized before being written to build logs, exposing sensitive credentials to anyone with access to those logs.

MitigationUpgrade TeamCity to version 2022.10 or later. Additionally, review build logs for any instances of exposed passwords from prior builds and rotate any compromised credentials as a precaution.

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

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
None
Availability
None

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

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

  1. Check TeamCity version
    Access the TeamCity server administration interface and navigate to 'About' or check the version via the server's root page. Alternatively, check the TeamCity logs or installation directory for version information.
    Affected if The installed version is any release before 2022.10 (e.g., 2022.09, 2022.07, earlier versions).
  2. Identify password-type build parameters
    Review your TeamCity project configurations and build steps for any parameters defined with the 'password' type. This is configured in the Parameters section of build configurations.
    Affected if There are build parameters configured as 'password' type in any build configuration.
  3. Inspect build logs for password exposure
    Examine recent build logs for any build that used password-type parameters. Look for entries where the password value appears in plain text rather than being masked as '******' or similar.
    Affected if Build logs contain unmasked password values from password-type parameters, especially if those passwords contain special characters.
  4. Review build log settings
    Check the TeamCity administration settings related to logging and the 'Verbose' logging options, as verbose logging may increase the likelihood of password exposure in logs.
    Affected if Verbose logging or debug logging was enabled for builds that used password-type parameters.

You are affected if running any TeamCity version before 2022.10 AND you have password-type build parameters that were used in builds, as those passwords may have been logged in plain text.

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 or later
Fixed in 2022.10
Interim mitigation

Upgrade TeamCity to version 2022.10 or later. Additionally, review build logs for any instances of exposed passwords from prior builds and rotate any compromised credentials as a precaution.

Recommended fix High confidence

TeamCity 2022.10 or later

  1. Backup your TeamCity installation and database before upgrading
  2. Review JetBrains TeamCity upgrade documentation for pre-upgrade requirements
  3. Upgrade TeamCity to version 2022.10 or later
  4. After upgrade, verify that password parameters with special characters are no longer exposed in build logs
  5. Confirm the upgrade was successful by checking the TeamCity server is operational
Caveat Review JetBrains release notes for any configuration or feature changes between your current version and 2022.10

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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