dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-39878

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 private key could be exposed via testing GitHub App 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 · high confidence

In JetBrains TeamCity before version 2024.03.3, the GitHub App Connection testing functionality improperly exposed private keys. This information disclosure vulnerability allows attackers with access to the exposed keys to potentially impersonate the configured GitHub App.

MitigationUpgrade TeamCity to version 2024.03.3 or later to receive the patch that prevents private key exposure during GitHub App Connection testing.

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. Identify TeamCity version
    Check the TeamCity server version by accessing the /about.html page or checking the buildServer.properties file in the TeamCity data directory. Compare the version number to 2024.03.3.
    Affected if The installed version is earlier than 2024.03.3 (for example, 2024.03.2, 2023.11.x, etc.)
  2. Determine if GitHub App Connection is configured
    Navigate to Administration > GitHub Settings > GitHub Apps in the TeamCity web interface, or check the TeamCity database for entries in the vcs_root table or similar configuration tables related to GitHub App connections.
    Affected if One or more GitHub App connections are configured in TeamCity
  3. Inspect server logs for key exposure indicators
    Search TeamCity server logs (under /logs/ directory) for entries related to GitHub App testing or connection testing around the time the feature was used. Look for patterns involving private key material or RSA keys.
    Affected if Logs contain raw private key data or RSA key content during GitHub App connection testing events
  4. Review audit logs for GitHub App connection tests
    Check TeamCity audit logs (typically found in the administration or logs section) for 'test connection' or 'verify' actions performed on GitHub App configurations.
    Affected if GitHub App connection testing was performed on the affected version

A user is affected if their TeamCity version is earlier than 2024.03.3 AND they have configured GitHub App connections that were tested or verified.

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 TeamCity to version 2024.03.3 or later to receive the patch that prevents private key exposure during GitHub App Connection testing.

Recommended fix High confidence

2024.03.3

  1. Backup your TeamCity database and configuration files before upgrading
  2. Review the TeamCity 2024.03.3 release notes for any specific upgrade requirements
  3. Ensure your current environment meets the system requirements for 2024.03.3
  4. Stop the TeamCity server service
  5. Upgrade TeamCity to version 2024.03.3 or later using the standard upgrade procedure
  6. Verify the upgrade was successful by checking the server starts correctly
  7. Test that GitHub App connections work properly after upgrade
  8. Confirm the private key is no longer exposed when testing GitHub App connections

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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