CVE-2024-47948
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 leading to information disclosure was possible via server backups
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 confidenceA path traversal vulnerability in JetBrains TeamCity versions prior to 2024.07.3 allows attackers to access arbitrary files on the server filesystem through the backup functionality by manipulating file paths in backup requests, leading to information disclosure.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check TeamCity server versionLocate the TeamCity version from the web UI (Administration > Diagnostics page) or from version.properties in the TeamCity data directoryAffected if The installed version is any release prior to 2024.07.3
-
Identify if backup functionality is enabledCheck if the backup feature is accessible by navigating to the Administration > Backup section or by confirming the /app/rest/backups API endpoint respondsAffected if The backup functionality is enabled and accessible to the attacker
-
Examine server logs for path traversal attemptsReview TeamCity server logs (typically in /logs directory) for backup API requests containing ../ sequences in file path parametersAffected if Log entries show backup requests with directory traversal patterns (../) targeting files outside the intended backup directory
You are affected if your TeamCity version is below 2024.07.3 and the backup functionality is accessible to untrusted users on your network.
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 to TeamCity 2024.07.3 or later to obtain the patch. If immediate patching is not feasible, restrict network access to the backup functionality and implement monitoring for anomalous backup API requests.
TeamCity 2024.07.3 or later
- 1. Back up your current TeamCity database and configuration files before starting the upgrade
- 2. Download TeamCity 2024.07.3 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
- 3. Stop the TeamCity server
- 4. Run the installer or deploy the new version following JetBrains standard upgrade documentation
- 5. Start the TeamCity server and verify all services are running correctly
- 6. Test that backup functionality works correctly and path traversal is no longer possible
- 7. Verify all projects and builds are functioning as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47948 — 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-47948 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