Cyber Resilience

CVE-2024-47949

Path Traversal in Jetbrains Teamcity ≤ 2024.07.3

Published
08 October 2024
Modified
11 October 2024
Patch / advisory
CVSS Score v3.1 4.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.23 98th percentile
Risk Priority 53 floored blend · peak EPSS

Summary

CVE-2024-47949 is a medium-severity Relative Path Traversal (CWE-23) vulnerability in Jetbrains Teamcity. Its CVSS base score is 4.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

In JetBrains TeamCity before 2024.07.3 path traversal allowed backup file write to arbitrary location

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-24942Same product: Jetbrains Teamcity
CVE-2024-27199Same product: Jetbrains Teamcity
CVE-2024-24938Same product: Jetbrains Teamcity
CVE-2025-46433Same product: Jetbrains Teamcity
CVE-2024-47948Same product: Jetbrains Teamcity
CVE-2024-36362Same product: Jetbrains Teamcity
CVE-2025-67742Same product: Jetbrains Teamcity
CVE-2024-54154Same vendor: Jetbrains
CVE-2024-24940Same vendor: Jetbrains
CVE-2024-8510Shared CWE-22, CWE-23

Affected Assets

jetbrains
teamcity
≤ 2024.07.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Explicit validation of path inputs stops .. sequences from ever being interpreted by the file system.

Information-flow rules can be configured to reject traversals that would move data outside an approved directory boundary.

Least privilege reduces the set of reachable files even when a traversal succeeds.

Secure-engineering principles require safe pathname construction and input neutralization before any file operation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent relative traversal.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches path traversal via static/dynamic analysis, but does not itself implement the fix.

prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent relative path traversal.

prevents

Application security requirements explicitly call for controls against path traversal and other injection flaws.

prevents

Secure architecture principles include directory isolation and canonicalization, reducing but not eliminating traversal risk.

prevents

Secure coding standards require neutralizing path traversal sequences, directly addressing CWE-23.

mitigates

Information access restriction limits which files can be reached, mitigating impact but not preventing the traversal flaw.

References