dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-41827

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 2024.07 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 2024.07 access tokens could continue working after deletion or expiration

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 2024.07, the access token validation mechanism fails to properly check token status in the database. When tokens are deleted or expire, they remain valid in active sessions because the token validation logic does not query the current status, allowing continued authentication using revoked or expired credentials.

MitigationUpgrade TeamCity to version 2024.07 or later to receive the patch. Additionally, revoke all existing access tokens and re-issue new tokens after the upgrade to ensure no stale tokens remain valid.

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:< 2024.07

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. Identify installed TeamCity version
    Access the TeamCity administration UI and navigate to 'About' page, or check the version from the startup logs, or query the /app/rest/server/version endpoint
    Affected if The installed version is any release before 2024.07 (e.g., 2024.06, 2024.05, older versions)
  2. Confirm access token authentication is in use
    Review TeamCity user settings or audit logs to identify if any users or integrations are using personal access tokens for authentication rather than password or SSO login
    Affected if Access tokens are created and actively used for API calls, CI/CD pipelines, or integration authentication
  3. Check for active user sessions
    In TeamCity administration, navigate to 'User Management' > 'Users' and review the 'Sessions' tab or check for lingering authenticated sessions in the database
    Affected if There are active user sessions that may have been authenticated using a token before it was revoked or expired
  4. Inspect token status in database
    Query the database table that stores access token information (typically tokens are stored in tables like user_tokens or similar) and compare token status with active server sessions
    Affected if Tokens marked as deleted or expired in the database still have corresponding valid sessions in the session table

You are affected if your TeamCity version is before 2024.07 AND you use access tokens for authentication, because revoked/expired tokens can remain valid in active sessions.

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

Upgrade TeamCity to version 2024.07 or later to receive the patch. Additionally, revoke all existing access tokens and re-issue new tokens after the upgrade to ensure no stale tokens remain valid.

Recommended fix High confidence

2024.07

  1. 1. Back up the TeamCity data directory and database before upgrading
  2. 2. Download TeamCity 2024.07 from the official JetBrains website (www.jetbrains.com)
  3. 3. Stop the TeamCity server gracefully
  4. 4. Install TeamCity 2024.07, ensuring to point to the existing data directory when prompted
  5. 5. Start the TeamCity server
  6. 6. Verify that access tokens are properly expired/deleted after their configured expiration time

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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