dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-36362

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-29
Fix available
A fix is available. Upgrade to 2022.04.7 / 2022.10.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 path traversal allowing to read files from server was possible

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

A path traversal vulnerability in JetBrains TeamCity allows attackers to escape the intended directory and access files outside the web root by using '..' sequences in file paths. This enables unauthorized read access to sensitive files on the server, including configuration files, credentials, or other system files.

MitigationUpgrade TeamCity to version 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 or later. If immediate patching is not possible, implement web application firewall rules to block traversal patterns in URL paths.

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:< 2022.04.7>= 2022.10, < 2022.10.6>= 2023.05, < 2023.05.6>= 2023.11, < 2023.11.5>= 2024.03, < 2024.03.2

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify installed TeamCity version
    Check the TeamCity server version by accessing the /about.html page on the TeamCity web interface, or by viewing the version in the TeamCity administration console under 'Server Administration > Diagnostics'. On the server filesystem, the version may also be listed in buildAgent/conf/buildAgent.properties or in the TeamCity logs.
    Affected if The version number falls into any of these ranges: < 2022.04.7; >= 2022.10 but < 2022.10.6; >= 2023.05 but < 2023.05.6; >= 2023.11 but < 2023.11.5; >= 2024.03 but < 2024.03.2.
  2. Confirm web interface is accessible
    Verify that the TeamCity web interface is reachable over HTTP/HTTPS. This vulnerability is exploitable through the web application, so the web endpoint must be exposed for the flaw to be actionable.
    Affected if The TeamCity web interface is accessible from a network where potential attackers could send requests.
  3. Check for sensitive file access attempts in logs
    Review TeamCity server logs (located in <TeamCity_HOME>/logs/ directory, particularly teamcity-server.log and teamcity-access-log.txt) for any entries containing '..' path traversal patterns in requested URLs. Search for patterns like '../', '..%2F', or encoded variations.
    Affected if Log analysis reveals any GET or POST requests containing traversal sequences ('..') targeting files outside the web root.

The environment is affected if the installed TeamCity version is within any of the vulnerable ranges listed and the web interface is accessible to potential attackers.

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 2022.04.7 / 2022.10.6 / 2023.05.6 or later
Fixed in 2022.04.72022.10.62023.05.6
Interim mitigation

Upgrade TeamCity to version 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 or later. If immediate patching is not possible, implement web application firewall rules to block traversal patterns in URL paths.

Recommended fix High confidence

2024.03.2

  1. 1. Back up your TeamCity data directory, database, and configuration files before upgrading.
  2. 2. Download TeamCity 2024.03.2 (or a later stable version) from the official JetBrains website: https://www.jetbrains.com/teamcity/download/
  3. 3. Stop the TeamCity server gracefully.
  4. 4. Follow the official TeamCity upgrade instructions to install the new version, preserving your existing data directory.
  5. 5. Start the TeamCity server and verify all services are running correctly.
  6. 6. Test that the path traversal vulnerability is no longer exploitable by verifying file access controls.
Caveat Review JetBrains release notes for any configuration or feature changes between your current version and 2024.03.2 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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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