CVE-2024-43809
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 reflected XSS was possible on the agentPushPreset 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 · high confidenceReflected XSS vulnerability in JetBrains TeamCity's agentPushPreset page allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in the HTTP response.
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
- 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 TeamCity versionLog into the TeamCity web interface and navigate to Administration > Global Settings, or check the buildServer.properties file for the version numberAffected if The installed version is lower than 2024.07.1
-
Verify agentPushPreset page existsNavigate to the agentPushPreset page via the TeamCity web UI or attempt to access it directly at /agentPushPreset.html or similar endpointAffected if The page exists and is accessible in the TeamCity installation
-
Confirm web interface is accessibleTest connectivity to the TeamCity web server HTTP/HTTPS endpointsAffected if The TeamCity web interface is reachable from a network where potential attackers could send malicious requests
-
Check authentication statusReview whether the agentPushPreset page requires authentication or is accessible to unauthenticated usersAffected if The page does not require authentication or is accessible to low-privilege users who could inject malicious scripts
You are affected if your TeamCity version is below 2024.07.1 AND the agentPushPreset page is accessible to users who could inject malicious script content that gets reflected back in the HTTP response.
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. Apply proper input validation and output encoding on the agentPushPreset page to prevent XSS attacks.
TeamCity 2024.07.1
- 1. Back up your TeamCity data, database, and configuration files before proceeding with the upgrade.
- 2. Download TeamCity version 2024.07.1 or later from the official JetBrains website (www.jetbrains.com).
- 3. Stop the TeamCity server gracefully.
- 4. Apply the upgrade following JetBrains standard upgrade procedures for your deployment type (installer or tarball).
- 5. Start the TeamCity server and verify all services are running correctly.
- 6. Test the agentPushPreset functionality to confirm the XSS vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43809 — 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-43809 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