dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-39879

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-01
Fix available
A fix is available. Upgrade to 2024.03.3 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 2024.03.3 application token could be exposed in EC2 Cloud Profile settings

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 prior to 2024.03.3, application tokens used for authentication are inadvertently exposed within EC2 Cloud Profile settings, potentially allowing unauthorized access to sensitive credentials.

MitigationUpgrade to TeamCity version 2024.03.3 or later to remediate the token exposure in EC2 Cloud Profile settings.

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.03.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
    Navigate to Administration > Global Settings or check the buildServer.properties file for the version number
    Affected if version is lower than 2024.03.3
  2. Verify EC2 Cloud Profile is configured
    Navigate to Administration > Cloud Profiles and look for EC2 cloud profile configurations
    Affected if EC2 Cloud Profile is present and configured
  3. Inspect EC2 Cloud Profile for exposed tokens
    Open each EC2 Cloud Profile and examine the settings for any stored application tokens or authentication credentials in plain text
    Affected if application tokens or credentials are visible in the EC2 Cloud Profile settings

User is affected if running TeamCity version below 2024.03.3 AND has EC2 Cloud Profiles configured with exposed authentication tokens

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.03.3 or later
Fixed in 2024.03.3
Interim mitigation

Upgrade to TeamCity version 2024.03.3 or later to remediate the token exposure in EC2 Cloud Profile settings.

Recommended fix Moderate confidence

2024.03.3

  1. Back up your TeamCity data and configuration before upgrading
  2. Download TeamCity version 2024.03.3 from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. Stop the TeamCity server
  4. Install the new version following the standard TeamCity upgrade procedure
  5. Start the TeamCity server and verify all services are running
  6. Review and re-save EC2 Cloud Profile settings to ensure credentials are properly re-encrypted

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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