dbcve.org
TeamcityApplication · Jetbrains

CVE-2022-24332

MEDIUM · 5.3 CVSS v3.1 Published 2022-02-25
Fix available
A fix is available. Upgrade to 2021.2 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 2021.2, a logout action didn't remove a Remember Me cookie.

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 2021.2, the logout functionality does not properly remove the Remember Me cookie (typically a persistent authentication token). This allows an attacker with access to the same browser or cookie storage to re-authenticate as the user even after explicitly logging out, since the persistent token remains valid.

MitigationUpgrade to TeamCity 2021.2 or later, which properly clears the Remember Me cookie on logout. As a workaround, users should clear browser cookies for the TeamCity instance after logging out.

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:< 2021.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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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
    Navigate to Administration > About in the TeamCity web UI, or query the API endpoint /app/rest/server/version. Compare the version number to the affected range (anything below 2021.2).
    Affected if The installed version is less than 2021.2.
  2. Verify Remember Me authentication is in use
    Go to Administration > Authentication > User Authentication settings and check if the Remember Me option is enabled for the authentication module.
    Affected if Remember Me authentication is enabled and the TeamCity version is below 2021.2.
  3. Inspect browser cookies for TeamCity
    Using browser developer tools, view cookies for the TeamCity domain. Look for persistent authentication tokens (often named similarly to tc-remember-me, remember-me, or a long alphanumeric token).
    Affected if Persistent Remember Me cookies exist for the TeamCity domain.
  4. Review authentication sessions
    Check Administration > User Management > User Sessions to see if sessions persist beyond logout times, indicating tokens remain valid after logout.
    Affected if Sessions remain active or can be re-established using old tokens after explicit logout.

The environment is affected if TeamCity version is below 2021.2 and the Remember Me feature is enabled, allowing stale cookies to re-authenticate users after logout.

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

Upgrade to TeamCity 2021.2 or later, which properly clears the Remember Me cookie on logout. As a workaround, users should clear browser cookies for the TeamCity instance after logging out.

Recommended fix High confidence

TeamCity 2021.2 or later

  1. 1. Back up the TeamCity server data and configuration files before upgrading.
  2. 2. Download TeamCity 2021.2 or a later stable version from the official JetBrains website.
  3. 3. Stop the TeamCity server instance.
  4. 4. Install the new TeamCity version following the official upgrade documentation.
  5. 5. Start the TeamCity server and verify the application is running correctly.
  6. 6. Test the logout functionality to confirm the Remember Me cookie is now properly removed on logout.
  7. 7. Monitor for any issues and review logs for errors.

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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