CVE-2024-43807
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.07.1 multiple stored XSS was possible on Clouds page
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 Clouds page allows authenticated users to inject malicious JavaScript that executes in browsers of other users viewing the Clouds page. The vulnerability exists in versions prior to 2024.07.1.
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.07.1CVSS 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 versionNavigate to Administration > About page in the TeamCity web UI, or check the version.txt file in the TeamCity installation directory, or inspect the buildAgent.properties file for the version fieldAffected if The installed version is any release prior to 2024.07.1 (e.g., 2024.06.x, 2024.05.x, earlier versions)
-
Verify Clouds page accessLog in as an authenticated user and navigate to Administration > Cloud Profiles (or Clouds page). Check if the user has permissions to view or create cloud profilesAffected if The authenticated user has access to the Clouds/Cloud Profiles page in TeamCity
-
Inspect cloud profile configurationsReview all cloud profiles under Administration > Cloud Profiles. Examine the profile name, description, and any custom parameters for unexpected script tags, event handlers, or JavaScript: URLsAffected if Any cloud profile contains script tags, onload/onerror event handlers, or javascript: protocol URLs in editable fields
A user is affected if their TeamCity installation is version 2024.07.1 or earlier AND they have authenticated users who can access the Clouds/Cloud Profiles page where malicious scripts could be injected and stored.
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.07.1
Upgrade TeamCity to version 2024.07.1 or later. Until patching is feasible, restrict administrative access to the Clouds page and implement Content Security Policy headers to mitigate XSS execution.
2024.07.1
- Back up your TeamCity data directory and database before upgrading
- Download TeamCity 2024.07.1 or later from the official JetBrains website (www.jetbrains.com)
- Stop the TeamCity server
- Install the new version following the standard upgrade procedure for your deployment method
- Start the TeamCity server
- Verify the Clouds page loads correctly and the stored XSS vulnerability is remediated
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-43807 — 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-43807 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