CVE-2024-31137
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 reflected XSS was possible via Space connection configuration
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 reflected cross-site scripting (XSS) vulnerability exists in JetBrains TeamCity versions prior to 2024.03. The vulnerability is specifically located in the Space connection configuration functionality, where unsanitized user input is reflected back in the application's response without proper encoding, allowing an attacker to inject malicious JavaScript code that executes in the victim's browser.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed TeamCity versionLog in to TeamCity as administrator and navigate to Administration > Server Administration > Server Configuration, or check the About page. Alternatively, check the logs or the version.txt file in the TeamCity home directory.Affected if The version displayed is any release prior to 2024.03 (for example, 2024.02, 2023.11, etc.)
-
Verify Space module is accessibleNavigate to the Administration menu and look for the Space section or Space connection configuration area. Check if the Space functionality is present in the user interface.Affected if The Space configuration interface is accessible and visible in the TeamCity Administration panel
-
Inspect Space connection configurationIn Administration > Space (or similar path), access any existing Space connection configurations. Look for fields where connection parameters such as URLs, names, or identifiers can be entered.Affected if There is an existing Space connection configuration with user-defined values present in the configuration fields
-
Check for unsanitized input reflectionTemporarily add a test string with special characters (such as <script>test</script> or javascript:alert(1)) into a Space connection configuration field and save. Then view the configuration page source or observe how the value is rendered back.Affected if The special characters are rendered literally in the response without HTML encoding, indicating the input is being reflected without sanitization
A user is affected if their TeamCity installation is version 2024.02 or earlier AND the Space connection configuration feature is accessible and reflects user input without proper HTML encoding.
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 to TeamCity version 2024.03 or later to receive the security patch. Review and sanitize any custom Space connection configurations, and consider implementing Content Security Policy headers as an additional defense-in-depth measure.
2024.03 or later (latest stable TeamCity release)
- Backup your TeamCity data and configuration before upgrading
- Download TeamCity 2024.03 or a later stable version from the official JetBrains website (www.jetbrains.com/teamcity/download)
- Stop the TeamCity server
- Install the new version following the standard TeamCity upgrade procedure
- Start the TeamCity server and verify all services are running
- Confirm the Space connection configuration works correctly and the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31137 — 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-31137 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