CVE-2024-36373
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 several stored XSS in untrusted builds settings were 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 · high confidenceStored cross-site scripting (XSS) vulnerability in JetBrains TeamCity allows malicious scripts to be injected through untrusted build settings and persisted on the server, potentially executing in the browsers of users viewing build configurations.
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.
-
Identify installed TeamCity versionAccess the TeamCity server administration interface and locate the Server Information page, or check the version displayed on the login page footer or About dialogAffected if The installed version is any release prior to 2024.03.2
-
Review build configuration accessCheck which users or user groups have permissions to create or modify build configurations in the TeamCity projectsAffected if Untrusted or low-privilege users can modify build settings, providing an injection vector
-
Examine build step parametersNavigate to Administration > Build Configurations and inspect the parameters, program arguments, and custom script fields in build steps for any unexpected or suspicious contentAffected if Any build configurations contain script content that was not authored by trusted administrators
-
Audit recent build configuration changesReview the audit log or history of build configuration modifications to identify any recent changes made to build settingsAffected if There are build configuration changes that contain encoded or obfuscated content that could represent injected scripts
You are affected if your TeamCity version is below 2024.03.2 and users can inject and persist malicious scripts through build configuration settings that execute when other users view those configurations.
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 JetBrains TeamCity to version 2024.03.2 or later to patch the stored XSS vulnerability in untrusted build settings.
TeamCity 2024.03.2
- Backup the existing TeamCity installation, data directory, and database
- Stop the TeamCity server service
- Download TeamCity 2024.03.2 from the official JetBrains website (www.jetbrains.com/teamcity/download)
- Run the installer or apply the update following JetBrains upgrade documentation
- Start the TeamCity server service
- Log in to the TeamCity web interface and verify the build configuration settings are accessible and functioning correctly
- Confirm the upgrade by checking the TeamCity version in Administration > Server Administration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36373 — 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-36373 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