CVE-2024-24937
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 2023.11.2 stored XSS via agent distribution 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 · high confidenceStored XSS vulnerability in JetBrains TeamCity's agent distribution feature allows attackers to inject malicious scripts that are persisted on the server and executed when other users interact with the affected agent distribution interface.
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< 2023.11.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.
-
Check TeamCity server versionNavigate to Administration > About in the TeamCity web UI, or check the version string in the server logs or startup outputAffected if The displayed version is earlier than 2023.11.2
-
Verify agent distribution feature usageCheck if any agent pools or agent configurations exist in the TeamCity interface under Administration > Agent PoolsAffected if Agent pools or agent configurations are present and the TeamCity version is below 2023.11.2
-
Review recent agent distribution settingsInspect any recently created or modified agent configurations, particularly any custom parameters or labels assigned to build agentsAffected if Custom agent parameters exist and the TeamCity version is below 2023.11.2
-
Audit user interactions with agent distributionReview server access logs for requests to agent-related endpoints, looking for suspicious script tags or unusual parameter patterns in distribution-related URLsAffected if Suspicious patterns are found in logs and the TeamCity version is below 2023.11.2
You are affected if your TeamCity installation version is earlier than 2023.11.2 and the agent distribution feature is in use.
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 · scoped2023.11.2
Upgrade TeamCity to version 2023.11.2 or later which contains the fix for this stored XSS vulnerability.
TeamCity 2023.11.2 or later
- Backup your current TeamCity data and configuration
- Download TeamCity version 2023.11.2 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
- Review JetBrains upgrade documentation for your deployment type
- Test the upgrade in a staging environment before applying to production
- Stop the TeamCity server
- Apply the upgrade following standard TeamCity upgrade procedures
- Start the TeamCity server and verify all services are running
- Verify the XSS vulnerability is resolved by checking that agent distribution no longer accepts unsanitized input
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-24937 — 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-24937 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