dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-41829

HIGH · 7.5 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 2024.07 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 before 2024.07 an OAuth code for JetBrains Space could be stolen via Space Application connection

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 versions before 2024.07, an OAuth authorization code intended for JetBrains Space application integration could be stolen, potentially allowing an attacker to impersonate a legitimate user and gain unauthorized access to the TeamCity instance via the compromised Space connection.

MitigationUpgrade TeamCity to version 2024.07 or later to patch the OAuth code theft vulnerability in the Space Application connection flow.

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
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. Verify TeamCity version
    Access the TeamCity administration interface and navigate to 'About TeamCity' or run the command to display the server version information.
    Affected if The installed version is earlier than 2024.07 (e.g., 2024.06, 2024.05, earlier) and the server is accessible over a network.
  2. Confirm Space application integration is configured
    Review TeamCity settings for OAuth providers, specifically looking for any configured JetBrains Space application connections in the authentication or integration settings.
    Affected if A JetBrains Space OAuth connection is actively configured or was recently configured in TeamCity.
  3. Inspect OAuth authorization flow logs
    Examine TeamCity server logs for OAuth-related entries, particularly focusing on authorization code exchange messages related to Space integration.
    Affected if Logs show authorization code requests or exchanges for Space applications that were not initiated by legitimate users.
  4. Review Space connection audit logs
    Check TeamCity audit logs or authentication logs for any Space application connections originating from unexpected IP addresses or occurring outside normal business patterns.
    Affected if Space connection events exist from IP addresses or locations not recognized as legitimate user sessions.

You are affected if your TeamCity version is before 2024.07 and you have JetBrains Space OAuth integration configured, as the stolen authorization code could allow attacker impersonation through the Space connection flow.

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 patch the OAuth code theft vulnerability in the Space Application connection flow.

Recommended fix High confidence

TeamCity 2024.07

  1. 1. Back up your current TeamCity installation, configuration, and database before proceeding
  2. 2. Download TeamCity 2024.07 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Follow the standard TeamCity upgrade procedure: stop the TeamCity server, run the installer or replace files with the new version, then start the server
  4. 4. After upgrade, verify the TeamCity server is running correctly
  5. 5. Test the OAuth connection to JetBrains Space to confirm the fix is working
  6. 6. Review the release notes for 2024.07 to ensure all new features and security fixes are understood
Caveat Review TeamCity 2024.07 release notes for any breaking changes from your current version

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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