CVE-2024-36374
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.2 stored XSS via build step settings was possible
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 confidenceStored XSS vulnerability in JetBrains TeamCity's build step settings allows authenticated attackers to inject malicious JavaScript code that executes when other users view or interact with the affected build configuration. The attack persists until the malicious configuration is removed or cleaned.
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.03.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify TeamCity versionNavigate to Administration > Server Administration > Server Configuration, or use the About link in the footer of any TeamCity page to display the exact version number.Affected if The installed version is lower than 2024.03.2 (for example, 2024.03.1, 2023.x, or earlier).
-
Access build step configurationsGo to Administration > Projects > select a project > Build Configurations > select a build configuration > click on Build Steps in the left navigation menu.Affected if You have access to view or edit build step settings in any build configuration.
-
Inspect build step scripts for malicious contentReview each build step listed under Build Steps. Examine the 'Script content' fields (for example, Command Line, PowerShell, Python scripts) for any suspicious JavaScript, HTML tags with event handlers (onerror, onload), or base64-encoded strings that could contain exploit payloads.Affected if Any build step contains unexpected or unrecognized script code, especially code that was not added by you or your team, or code containing patterns like <script>, javascript:, onerror=, onload=, or eval(atob(...)).
You are affected if your TeamCity version is below 2024.03.2 AND you discover unauthorized or malicious script content in any build step configuration that you did not create.
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.2
Upgrade TeamCity to version 2024.03.2 or later to receive the security fix. Review existing build step configurations for any suspicious scripts and remove them.
TeamCity 2024.03.2
- Back up your TeamCity data and configuration before upgrading
- Download TeamCity 2024.03.2 or later from the official JetBrains website (https://www.jetbrains.com/teamcity/download/)
- Stop the TeamCity server
- Follow the official TeamCity upgrade instructions to install the new version
- Start the TeamCity server and verify the upgrade was successful
- Verify that the stored XSS vulnerability in build step settings is no longer present
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-36374 — 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-36374 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