dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-35300

MEDIUM · 6.1 CVSS v3.1 Published 2024-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
In JetBrains TeamCity between 2024.03 and 2024.03.1 several stored XSS in the available updates page were 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 confidence

Stored cross-site scripting (XSS) vulnerability in JetBrains TeamCity versions 2024.03 through 2024.03.1. The flaw exists in the 'available updates' page where malicious scripts can be injected and persistently stored, executing when other users view the affected page.

MitigationUpgrade TeamCity to version 2024.03.2 or later. If immediate patching is not possible, restrict access to the updates page to trusted administrators only.

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
TeamcityApplication
Affected:= 2024.03

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check TeamCity server version
    Log into the TeamCity administrative interface and navigate to Administration > Server Administration > Server Configuration. The version is displayed on the main server information page or in the footer of the web interface.
    Affected if The installed version is 2024.03 or 2024.03.1 (versions 2024.03 through 2024.03.1 are affected)
  2. Confirm access to the available updates page
    Navigate to Administration > Server Administration > Available Updates. This page displays information about available updates for the TeamCity installation.
    Affected if The page loads successfully and displays update information, indicating the vulnerable feature is enabled
  3. Inspect page source for potential XSS vectors
    Right-click on the Available Updates page and select View Page Source. Examine the HTML output for any user-controlled fields that might be reflected without proper encoding, particularly version numbers, update descriptions, or plugin names.
    Affected if The page source shows unescaped HTML characters in update-related fields that could be manipulated
  4. Review server logs for XSS indicators
    Examine TeamCity server logs located in the <TeamCity data directory>/logs directory, particularly teamcity-server.log and teamcity-events.log, for any unusual script tags or JavaScript code patterns in update-related entries.
    Affected if Logs contain script tags or JavaScript code snippets associated with the Available Updates functionality

You are affected if your TeamCity installation is version 2024.03 or 2024.03.1 and the Available Updates page is accessible to administrators.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade TeamCity to version 2024.03.2 or later. If immediate patching is not possible, restrict access to the updates page to trusted administrators only.

Recommended fix High confidence

2024.03.1

  1. 1. Back up your TeamCity instance before performing any upgrade
  2. 2. Download TeamCity 2024.03.1 from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Review the upgrade notes for 2024.03.1 for any specific migration requirements
  4. 4. Stop the TeamCity server
  5. 5. Install version 2024.03.1 following the standard upgrade procedure
  6. 6. Verify the upgrade was successful by logging into the web interface
  7. 7. Confirm the 'available updates' page no longer contains the XSS vulnerability
Caveat Review JetBrains release notes for any configuration or compatibility changes between 2024.03 and 2024.03.1

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35300 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-35300 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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