dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-24942

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-06
Fix available
A fix is available. Upgrade to 2023.11.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 2023.11.3 path traversal allowed reading data within JAR archives

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

A path traversal vulnerability in JetBrains TeamCity versions before 2023.11.3 allows attackers to read data within JAR archives on the server. By manipulating file paths, an attacker could potentially access sensitive files embedded in JAR archives.

MitigationUpgrade TeamCity to version 2023.11.3 or later to patch the path traversal vulnerability in JAR archive handling.

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.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. Locate TeamCity installation and version
    Access the TeamCity administration interface and navigate to 'About' page, or check the buildserver.version parameter via the REST API at /app/rest/server/version
    Affected if The installed version is any version before 2023.11.3 (e.g., 2023.11.2, 2023.11.1, earlier releases)
  2. Verify TeamCity web interface is accessible
    Confirm the TeamCity web server is running and reachable at its configured hostname or IP address
    Affected if TeamCity is exposed over HTTP/HTTPS and accepts file processing requests
  3. Check for JAR archive processing capability
    Identify if TeamCity is configured to process or serve JAR files as part of build artifacts, dependencies, or plugins
    Affected if TeamCity has any project, build configuration, or plugin that handles or serves JAR archives to users or external systems
  4. Review access logs for suspicious JAR path traversal requests
    Examine TeamCity server logs (typically in /logs/ directory) and HTTP access logs for patterns like '../' or '..\' sequences in JAR file paths
    Affected if Logs show requests with directory traversal sequences targeting JAR files that fall outside expected directories

You are affected if TeamCity version is below 2023.11.3 AND the server is accessible over the network AND handles JAR archive processing.

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.3 or later
Fixed in 2023.11.3
Interim mitigation

Upgrade TeamCity to version 2023.11.3 or later to patch the path traversal vulnerability in JAR archive handling.

Recommended fix High confidence

TeamCity 2023.11.3 or later

  1. Identify current TeamCity version from the Administration > Global Settings page
  2. Review TeamCity release notes for 2023.11.3 for any migration requirements
  3. Create a complete backup of the TeamCity data directory (by default <TeamCity data directory>/system)
  4. Stop the TeamCity server service
  5. Download TeamCity 2023.11.3 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
  6. Install the new version following the standard upgrade procedure documented in TeamCity documentation
  7. Start the TeamCity server service and verify the upgrade completed successfully
  8. Verify the new version is showing in Administration > Global Settings
Caveat Standard upgrade considerations apply - review release notes for any configuration or migration changes between your current version and 2023.11.3

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
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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