JetBrains TeamCity Relative Path Traversal Vulnerability
JetBrains TeamCity contains a relative path traversal vulnerability that could allow limited admin actions to be performed.
Quick answer
JetBrains TeamCity should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
Treat CVE-2024-27199 as an actively exploited JetBrains TeamCity On-Premises path traversal issue. JetBrains says all TeamCity On-Premises versions through 2023.11.3 are affected and the fix is in 2023.11.4; JetBrains also provides a security patch plugin for environments that cannot upgrade immediately. Prioritize internet-facing TeamCity servers and any instance with build credentials, deployment keys, signing keys, or source-control tokens. After patching, assume secrets exposed to the TeamCity server may need rotation if compromise is suspected.
- Inventory every TeamCity On-Premises server, proxy hostname, agent pool, plugin installation, and internet-facing TeamCity URL.
- Identify all TeamCity versions through 2023.11.3 as affected.
- Upgrade TeamCity On-Premises to 2023.11.4 or later using JetBrains-supported upgrade procedures.
- If an immediate upgrade is not possible, install the JetBrains security patch plugin on the affected TeamCity server as a temporary mitigation.
- Restrict TeamCity access to trusted networks, SSO, VPN, or approved reverse-proxy controls until remediation is verified.
- Review TeamCity audit logs, user accounts, access tokens, build configurations, plugins, and server logs for suspicious admin actions or path traversal attempts.
- Rotate VCS credentials, build secrets, deployment keys, runner tokens, and signing keys if unauthorized access is suspected.
- Rebuild affected TeamCity servers or agents from trusted backups if compromise indicators are found.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm TeamCity reports version 2023.11.4 or later, or confirm the JetBrains security patch plugin is installed as an interim control.
- Confirm TeamCity Cloud is not in scope unless a self-managed TeamCity On-Premises server is also used.
- Confirm vulnerability management no longer flags CVE-2024-27199 on TeamCity hosts.
- Review post-remediation TeamCity logs for continued traversal attempts or unexpected administrative activity.
- Run a Fixnx scan against public TeamCity hostnames to confirm exposure is reduced.
Related categories
Trusted references
FAQ
What is affected by CVE-2024-27199?
JetBrains TeamCity should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
Why can this risk appear in multiple categories?
A vulnerability can belong to more than one platform or ecosystem. Fixnx keeps one canonical risk page while also listing it in every relevant category.