CVE-2024-31139 json
In JetBrains TeamCity before 2024.03 xXE was possible in the Maven build steps detector
published 2y ago modified 4mo ago also EUVD-2024-29050
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
In JetBrains TeamCity before 2024.03 xXE was possible in the Maven build steps detector
Patch / fix
- JetBrains TeamCity 2024.03
Is CVE-2024-31139 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:H |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
Affected products
- JetBrains TeamCity
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
jetbrains.com
/privacy-security/issues-fixed/
vendor-advisory
Sources
- CVE List CVE-2024-31139
- NVD CVE-2024-31139
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.