dbcve.org
TeamcityApplication · Jetbrains

CVE-2023-41249

MEDIUM · 6.1 CVSS v3.1 Published 2023-08-25
Fix available
A fix is available. Upgrade to 2023.05.3 or later.
See remediation →
68/100
Remediation priority · Elevated
High EPSS 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.05.3 reflected XSS was possible during copying Build Step

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

A reflected cross-site scripting (XSS) vulnerability in JetBrains TeamCity versions prior to 2023.05.3 allows attackers to inject malicious scripts through the Build Step copying functionality. The vulnerability occurs when user-supplied input in the Build Step copy operation is insufficiently sanitized before being reflected back in the HTTP response.

MitigationUpgrade JetBrains TeamCity to version 2023.05.3 or later. If immediate upgrading is not possible, implement strict input validation and output encoding on the Build Step copy functionality, and consider restricting web interface access until the patch is applied.

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.05.3

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
    Log into the TeamCity web interface as an administrator and navigate to the Administration > Server Administration > Server Information page, or check the <TeamCity home>/buildAgent/conf/buildAgent.properties file for the version property. Alternatively, access the /app/server/version endpoint if exposed.
    Affected if The displayed version number is lower than 2023.05.3 (for example, 2023.05.2, 2023.04.x, or earlier)
  2. Locate the Build Step copy feature
    In the TeamCity web interface, navigate to a project, then to a build configuration, and examine the Build Steps page. Look for an option to copy or duplicate an existing build step, typically represented by a copy icon or 'Clone'/'Copy' button next to a build step entry.
    Affected if The Build Step copy functionality is present and accessible in the interface
  3. Check for unauthenticated or low-privilege access
    Determine whether users with limited privileges (such as project viewer or build configuration viewer roles) can access the Build Step copy functionality, or test copying a build step while capturing the HTTP request and response with a web proxy.
    Affected if User-supplied input in the Build Step copy operation is reflected in the HTTP response without visible sanitization or encoding

You are affected if your installed TeamCity version is below 2023.05.3 and the Build Step copy feature is accessible in your web interface, as the insufficiently sanitized user input would be reflected back in the response.

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.05.3 or later
Fixed in 2023.05.3
Interim mitigation

Upgrade JetBrains TeamCity to version 2023.05.3 or later. If immediate upgrading is not possible, implement strict input validation and output encoding on the Build Step copy functionality, and consider restricting web interface access until the patch is applied.

Recommended fix High confidence

TeamCity 2023.05.3 or later

  1. Backup your TeamCity data and configuration before upgrading
  2. Download TeamCity 2023.05.3 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. Stop the TeamCity server
  4. Follow the official TeamCity upgrade instructions for your installation type
  5. Start the TeamCity server after upgrade completes
  6. Verify the Build Step copy functionality works correctly and the XSS vulnerability is resolved
Caveat Review TeamCity 2023.05.3 release notes for any configuration or feature changes before upgrading

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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