CVE-2024-31139
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.03 xXE was possible in the Maven build steps detector
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 confidenceTeamCity before version 2024.03 contains an XML External Entity (XXE) injection vulnerability in the Maven build steps detector. This allows attackers to exploit the XML parser to potentially read local files or perform server-side request forgery via malicious XML input.
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.03CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
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 installation and versionCheck the TeamCity server UI (about page) or run: `java -jar teamcity-version.jar` from the TeamCity bin directory, or check the buildServer.properties file for the version numberAffected if The installed version is any version prior to 2024.03 (e.g., 2023.11, 2023.05, etc.)
-
Determine if Maven build steps feature is in useReview TeamCity project configurations for any build steps configured as Maven type (check build configurations, .teamcity/pom.xml files, or project settings in the TeamCity web UI)Affected if Maven build steps are configured in any project or template within the TeamCity server
-
Verify XML processing occurs in Maven build detectionInspect TeamCity logs or Maven build step configurations to confirm XML parsing is triggered during build import or Maven artifact detectionAffected if The Maven build steps detector processes XML files (such as pom.xml) as part of its normal operation
You are affected if your TeamCity installation version is below 2024.03 and you have Maven build steps configured, as the XXE vulnerability exists in the Maven build steps detector's XML parser.
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.03
Upgrade TeamCity to version 2024.03 or later to patch the XXE vulnerability in the Maven build steps detector.
2024.03
- Create a complete backup of the TeamCity data directory and database before upgrading
- Stop the TeamCity server
- Download TeamCity 2024.03 or a later stable version from the official JetBrains distribution channels
- Install the new version following the standard TeamCity upgrade procedure
- Start the TeamCity server and verify all Maven build steps are functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31139 — 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-31139 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