dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-29880

HIGH · 7.8 CVSS v3.1 Published 2024-03-21
Fix available
A fix is available. Upgrade to 2023.11 or later.
See remediation →
80/100
Remediation priority · High
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 2023.11 users with access to the agent machine might obtain permissions of the user running the agent process

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

Local privilege escalation vulnerability in JetBrains TeamCity versions before 2023.11 where users with access to the agent machine can obtain the permissions of the user running the agent process. This allows an attacker with machine-level access to elevate privileges to the agent's running user context.

MitigationUpgrade to TeamCity version 2023.11 or later. Additionally, restrict physical and logical access to agent machines to trusted personnel only.

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

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

CVSS:3.1/AV:L/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. Identify TeamCity installation
    Look for TeamCity installation directories or check for TeamCity services/processes on the system. Common locations include /opt/TeamCity, C:\TeamCity, or directories under Program Files on Windows.
    Affected if TeamCity is not found on the system - not applicable
  2. Confirm this is a TeamCity agent
    Check if the installed TeamCity instance is configured as an agent (not the server). Examine the configuration files or process details - agent installations typically have a buildAgent directory and communicate with a TeamCity server.
    Affected if This is a TeamCity server-only installation - not affected by this agent-specific vulnerability
  3. Determine the installed TeamCity version
    Check the version of the TeamCity agent installation. Look for version information in the agent's about screen, version file, or startup logs. Compare the version number against the 2023.11 threshold.
    Affected if Version is 2023.11 or later - not affected. Version is before 2023.11 - potentially affected
  4. Verify the agent process is running
    Check if the TeamCity agent process is currently active on the system using process monitoring tools (such as task manager on Windows or ps/top on Linux). The vulnerability requires the agent to be running for privilege escalation to occur.
    Affected if Agent process is not running - low immediate risk but still vulnerable when started
  5. Assess physical and logical access to the agent machine
    Review who has access to the machine hosting the TeamCity agent. The vulnerability requires an attacker to have machine-level access to exploit the privilege escalation.
    Affected if Untrusted or insufficiently restricted personnel have access to the agent machine - higher exposure to this vulnerability

If the system runs a TeamCity agent version earlier than 2023.11, and untrusted users can access that machine, the environment is affected by this privilege escalation vulnerability.

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

Upgrade to TeamCity version 2023.11 or later. Additionally, restrict physical and logical access to agent machines to trusted personnel only.

Recommended fix High confidence

TeamCity 2023.11 or later

  1. Create a full backup of your TeamCity installation including the <TeamCity home> directory and database
  2. Stop the TeamCity server and all running agents
  3. Download TeamCity 2023.11 or a later stable version from the official JetBrains website (www.jetbrains.com)
  4. Follow the standard TeamCity upgrade instructions for your operating system
  5. Start the TeamCity server and verify all services are running correctly
  6. Confirm the upgrade was successful by checking the TeamCity version in the administration UI
Caveat Review JetBrains release notes for 2023.11 for any configuration or plugin compatibility changes before upgrading

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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