dbcve.org
TeamcityApplication · Jetbrains

CVE-2022-48427

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-27
Fix available
A fix is available. Upgrade to 2022.10.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 2022.10.3 stored XSS on “Pending changes” and “Changes” tabs 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 confidence

Stored XSS vulnerability in JetBrains TeamCity's 'Pending changes' and 'Changes' tabs allows authenticated attackers to inject malicious scripts that execute in the browsers of other users viewing these change tracking pages.

MitigationUpgrade TeamCity to version 2022.10.3 or later to patch the stored XSS vulnerability in the change tracking pages.

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:< 2022.10.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. Check TeamCity server version
    Navigate to the TeamCity web UI, click on the 'Administration' section, then 'Server Administration', and view the 'Server Version' displayed on the page. Alternatively, check the version from the startup logs or the <TeamCity_home>/buildAgent/lib directory.
    Affected if The installed version is any release earlier than 2022.10.3 (e.g., 2022.10.2, 2022.10.1, etc.)
  2. Confirm access to change tracking pages
    Log in to TeamCity as an authenticated user and navigate to any project, then locate the 'Changes' or 'Pending changes' tab in the navigation menu.
    Affected if The user has access to view these change tracking pages and the TeamCity version is below 2022.10.3
  3. Verify user authentication is enabled
    Check that TeamCity's user authentication is active by confirming users require login credentials to access the server.
    Affected if The server allows authenticated users to submit changes and the installed version is below 2022.10.3

A user is affected if their TeamCity installation version is below 2022.10.3 and they have access to the 'Pending changes' or 'Changes' tabs.

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 2022.10.3 or later
Fixed in 2022.10.3
Interim mitigation

Upgrade TeamCity to version 2022.10.3 or later to patch the stored XSS vulnerability in the change tracking pages.

Recommended fix High confidence

2022.10.3

  1. Upgrade JetBrains TeamCity to version 2022.10.3 or later

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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