dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-35302

MEDIUM · 6.1 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 2023.11 or later.
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 before 2023.11 stored XSS during restore from backup 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 · moderate confidence

A stored cross-site scripting (XSS) vulnerability exists in JetBrains TeamCity versions prior to 2023.11. The vulnerability is triggered during the restore from backup functionality, allowing an attacker to inject malicious scripts that are executed when the backup is restored.

MitigationUpgrade TeamCity to version 2023.11 or later to receive the security patch. Review and validate backup files before restoration as an additional precaution.

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:< 2023.11

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. Identify TeamCity version
    Navigate to Administration > Server Administration > Server Configuration, or check the bottom-left corner of the TeamCity web interface for the version number
    Affected if The version displayed is earlier than 2023.11 (for example, 2023.10.4, 2023.9, etc.)
  2. Confirm backup restore is accessible
    Check if the backup and restore functionality is enabled in TeamCity. Navigate to Administration > Server Administration > Backup or verify that the backup/restore plugin is loaded
    Affected if Backup restore functionality is available and enabled on the server
  3. Verify backup restoration permissions
    Review user roles and permissions in Administration > User Management > Roles to see which users have the 'Restore' or 'Backup' permission
    Affected if Users with limited or no administrative privileges can access the restore from backup feature
  4. Audit existing backup files
    Locate backup files in the <TeamCity Data Directory>/backup directory or configured backup storage location. Inspect file metadata or any XML/JSON configuration files within backups for suspicious script tags
    Affected if Any backup file contains unexpected script tags, event handlers, or encoded JavaScript content in fields that accept user input

The environment is affected if TeamCity version is earlier than 2023.11 AND the backup restore functionality is accessible to users who could potentially inject or restore malicious content.

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
Upgrade available Upgrade to 2023.11 or later
Fixed in 2023.11
Interim mitigation

Upgrade TeamCity to version 2023.11 or later to receive the security patch. Review and validate backup files before restoration as an additional precaution.

Recommended fix Moderate confidence

TeamCity 2023.11 or later

  1. Back up your current TeamCity installation including the <TeamCity Data Directory> and database
  2. Download TeamCity 2023.11 or later from the official JetBrains website
  3. Stop the TeamCity server
  4. Run the TeamCity installer or extract the new version to the installation directory
  5. Start the TeamCity server - the upgrade will be applied automatically
  6. Verify the upgrade was successful by logging into TeamCity and checking the version number under Administration > Diagnostics > About

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Check whether your project pulls in CVE-2024-35302 — 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-35302 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