dbcve.org
TeamcityApplication · Jetbrains

CVE-2023-41248

MEDIUM · 5.4 CVSS v3.1 Published 2023-08-25
Fix available
A fix is available. Upgrade to 2023.05.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 stored XSS was possible during Cloud Profiles 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 · moderate confidence

Stored cross-site scripting (XSS) vulnerability in JetBrains TeamCity's Cloud Profiles configuration allows attackers to inject malicious JavaScript through Cloud Profile settings. The payload is stored persistently and executes when administrators view or manage the cloud profile configuration.

MitigationUpgrade TeamCity to version 2023.05.3 or later which contains the fix for this stored XSS vulnerability in Cloud Profiles. Alternatively, restrict administrative access to Cloud Profiles configuration until the upgrade can be performed.

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

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

  1. Identify TeamCity version
    Check the TeamCity server version by accessing the About page (usually at /about.html on the TeamCity server) or checking the teamcity-server.log file for version information
    Affected if The installed version is any version prior to 2023.05.3 (for example, 2023.05.2, 2023.05.1, 2023.03.x, or earlier)
  2. Verify Cloud Profiles feature is in use
    Navigate to Administration > Cloud Profiles in the TeamCity web UI, or check the database for entries in the cloud_profiles table if database access is available
    Affected if Cloud Profiles are configured and active in the TeamCity instance
  3. Inspect Cloud Profile configurations for suspicious content
    Review each Cloud Profile's settings (profile name, description, image URL, and other configurable fields) through the web UI or by querying the database for any HTML or script tags within profile metadata
    Affected if Any Cloud Profile contains unescaped HTML, script tags, or javascript: URLs in its configuration fields
  4. Review audit and access logs
    Examine TeamCity audit logs and server access logs for unusual POST requests to Cloud Profile API endpoints that may indicate exploitation attempts
    Affected if Logs show suspicious requests containing script tags or encoded JavaScript targeting cloud profile configuration endpoints

A user is affected if their TeamCity installation is version 2023.05.3 or earlier AND Cloud Profiles are configured, as the XSS payload would be stored in Cloud Profile settings and execute when administrators view those configurations.

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 TeamCity to version 2023.05.3 or later which contains the fix for this stored XSS vulnerability in Cloud Profiles. Alternatively, restrict administrative access to Cloud Profiles configuration until the upgrade can be performed.

Recommended fix High confidence

2023.05.3

  1. 1. Back up your TeamCity server data and configuration before proceeding with the upgrade.
  2. 2. Download TeamCity 2023.05.3 or a later stable version from the official JetBrains website (www.jetbrains.com/teamcity/download).
  3. 3. Stop the TeamCity server service.
  4. 4. Install the new version following the standard TeamCity upgrade documentation.
  5. 5. Start the TeamCity server and verify the Cloud Profiles functionality works correctly.
  6. 6. Test that the stored XSS vulnerability in Cloud Profiles configuration is no longer present.

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-41248 — 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-41248 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