CVE-2024-47949
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 · uneditedIn JetBrains TeamCity before 2024.07.3 path traversal allowed backup file write to arbitrary location
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 confidenceA path traversal vulnerability in JetBrains TeamCity versions before 2024.07.3 allows attackers to write backup files to arbitrary locations on the server filesystem via the backup functionality. This could enable remote code execution or system compromise.
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< 2024.07.3CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify TeamCity versionNavigate to Administration > Diagnostics > About in the TeamCity web UI, or check the buildServer.properties file for the version numberAffected if The installed version is below 2024.07.3
-
Verify backup feature exposureCheck if the /admin/backup.html or /app/rest/backups endpoints are accessible without authentication or from unauthorized network locationsAffected if Backup functionality is exposed to untrusted users or networks
-
Review backup configurationExamine TeamCity server logs and backup configuration files for unexpected or unauthorized backup operationsAffected if Backup files exist in directories outside the designated TeamCity data directory
-
Audit server filesystemSearch for .zip or .tar.gz backup files in unexpected locations such as /tmp, /var/tmp, or web root directoriesAffected if Backup archives are present outside the designated backup storage path
If TeamCity version is below 2024.07.3 AND the backup feature is accessible to attackers, the environment is vulnerable to path traversal during backup operations
Generated from the published advisory. Verify against your own configuration.
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 · scoped2024.07.3
Upgrade JetBrains TeamCity to version 2024.07.3 or later. If immediate patching is not possible, restrict network access to the TeamCity administration interfaces and monitor for suspicious backup operations.
2024.07.3
- Review the TeamCity 2024.07.3 release notes to confirm the path traversal vulnerability (CVE-2024-47949) is addressed
- Create a full backup of the current TeamCity installation including the <TeamCity home> directory and database
- Stop the TeamCity server service
- Upgrade TeamCity to version 2024.07.3 or later following the standard upgrade procedure
- Start the TeamCity server and verify the service is running correctly
- Test the backup functionality to confirm the path traversal fix is working as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47949 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47949 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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