CVE-2023-43566
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.05.4 stored XSS was possible during nodes configuration
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's nodes configuration interface allows authenticated attackers to inject malicious scripts that execute when other users view the affected configuration pages.
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.05.4CVSS 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 administration interface and navigate to the 'About' page, or run the command: `cat <TeamCity_installation_directory>/buildAgent/conf/buildAgent.properties | grep version` to view the version numberAffected if The installed version is lower than 2023.05.4 (for example, 2023.05.3, 2023.05, 2023.04.x, or earlier)
-
Verify nodes configuration interface is accessibleLog into TeamCity as an authenticated user with administrative privileges and navigate to Administration > Server Administration > Nodes, or access the nodes configuration page directly via the URL path containing 'nodes' in the TeamCity web interfaceAffected if The nodes configuration interface is accessible and visible in the administration menu
-
Inspect node configuration data for suspicious contentReview all existing node configurations stored in the TeamCity database or configuration files. Look for any script tags, JavaScript event handlers, or encoded payloads within node name, description, URL, or other configuration fieldsAffected if Any node configuration entries contain raw script tags, javascript: URLs, or HTML elements with event handlers such as onload, onerror, or onclick
-
Check browser console or access logs for XSS indicatorsIf you have access to the TeamCity server logs, search for repeated or unusual patterns in HTTP access logs that may indicate XSS probe attempts targeting the nodes configuration endpointAffected if Access logs show suspicious requests with XSS payloads submitted to node configuration endpoints
You are affected if your TeamCity version is below 2023.05.4 AND the nodes configuration interface is accessible to authenticated users, particularly if any node configurations contain unsanitized script content.
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.05.4
Upgrade to TeamCity version 2023.05.4 or later. Additionally, review and sanitize any existing node configurations for malicious input.
TeamCity 2023.05.4 or latest stable release
- 1. Back up your current TeamCity data directory (by default <TeamCity Data Directory>)
- 2. Download TeamCity 2023.05.4 or later from the official JetBrains website (https://www.jetbrains.com/teamcity/download/)
- 3. Stop the TeamCity server
- 4. If upgrading from a significantly older version, review the upgrade notes in JetBrains documentation
- 5. Install the new version, pointing to your existing data directory when prompted
- 6. Start the TeamCity server
- 7. Verify the nodes configuration functionality works correctly and the XSS vulnerability is resolved
- 8. Clear browser cache and test that the stored XSS is no longer executable in the nodes configuration area
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43566 — 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-2023-43566 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