Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LSummary
CVE-2024-27199 is a high-severity Relative Path Traversal (CWE-23) vulnerability in Jetbrains Teamcity. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.0% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
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.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-27199 is a path traversal vulnerability, tracked under CWE-23 and CWE-22, that affects JetBrains TeamCity versions prior to 2023.11.4. The flaw permits unauthorized access to perform a limited set of administrative actions on the server. It carries a CVSS 3.1 base score of 7.3, reflecting network attack vector, low complexity, and no required authentication or user interaction.
Unauthenticated remote attackers can exploit the issue over the network to conduct limited administrative operations that would normally require elevated privileges. Successful exploitation can lead to partial compromise of confidentiality, integrity, and availability within the TeamCity instance.
JetBrains has addressed the vulnerability in TeamCity 2023.11.4 and later releases, as documented on its official security issues page. Administrators are advised to apply the available updates promptly to eliminate the path traversal vector.
Public reporting indicates active mass exploitation of the flaw in the wild, with threat actors creating rogue administrative accounts. The associated EPSS score has reached a peak of 0.9449 and currently stands at 0.9093, while proof-of-concept code has been published on GitHub.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-24438
Vulnerability Data
In JetBrains TeamCity before 2023.11.4 path traversal allowing to perform limited admin actions was possible
- CWE(s)
- KEV Date Added
- 20 April 2026
Related Threats
Threat-Actor AttributionAI
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
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.
Secure SDLC practices directly require input validation and path sanitization that prevent relative traversal.
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 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.
Security testing in development catches path traversal via static/dynamic analysis, but does not itself implement the fix.
Secure development lifecycle mandates input validation and path-handling controls that directly prevent relative path traversal.
Application security requirements explicitly call for controls against path traversal and other injection flaws.
Secure architecture principles include directory isolation and canonicalization, reducing but not eliminating traversal risk.
Secure coding standards require neutralizing path traversal sequences, directly addressing CWE-23.
Information access restriction limits which files can be reached, mitigating impact but not preventing the traversal flaw.