CVE-2024-36372
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.6 reflected XSS on the subscriptions page 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 confidenceReflected XSS vulnerability in JetBrains TeamCity subscriptions page allows attackers to inject malicious scripts via unsanitized user input that gets reflected back in the response. This requires tricking a user into clicking a crafted link, potentially leading to session hijacking or theft of sensitive information.
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.6CVSS 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.
-
Identify installed TeamCity versionLog into the TeamCity web interface and navigate to the 'About' page (Administration > Server Administration > Server Information) to view the exact version number. Alternatively, check the version.log file in the TeamCity logs directory or the buildConfig.properties file in the TeamCity data directory.Affected if The version displayed is earlier than 2023.05.6 (for example, 2023.05.5, 2023.05.4, 2023.11.x, etc.)
-
Verify subscriptions page is accessibleNavigate to the subscriptions page endpoint in TeamCity. The typical path is /subs.html or /admin/subscriptions.html depending on your TeamCity version. Attempt to access this page while authenticated as a regular user or administrator.Affected if The page loads and accepts URL parameters without visible sanitization or encoding of special characters
-
Test for reflected input in URL parametersOn the subscriptions page, observe the URL structure and attempt to add a test parameter with a benign payload such as '?test=<script>alert(1)</script>' or '&test=xss'. Check if this input is reflected back in the HTML response without encoding.Affected if The injected string appears unescaped in the page source (visible as actual <script> tags or HTML elements rather than encoded entities like <script>)
If the installed TeamCity version is below 2023.05.6 and the subscriptions page reflects URL parameters back into the HTML response without proper encoding, the environment is vulnerable to this reflected XSS.
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.6
Upgrade TeamCity to version 2023.05.6 or later. If immediate upgrade is not possible, implement URL parameter validation and output encoding on the subscriptions page as compensating controls.
2023.05.6
- Download and install TeamCity version 2023.05.6 or later from the official JetBrains website
- Restart the TeamCity server after upgrading
- Log in to TeamCity and navigate to the Administration > Diagnostics > Subscriptions page to verify the page loads without errors
- Confirm that the XSS vulnerability is remediated by verifying that user-supplied input on the subscriptions page is properly sanitized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36372 — 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-36372 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