CVE-2022-48343
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 · uneditedIn JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the user creation process.
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability existed in the user creation functionality of JetBrains TeamCity versions prior to 2022.10.2, allowing an attacker to inject malicious JavaScript code through user profile fields during account creation.
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< 2022.10.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed TeamCity versionAccess the TeamCity Administration > Diagnostics page or check the buildServer.properties file for the version number. Alternatively, access the /app/rest/server/version endpoint if REST API is enabled.Affected if The installed version is lower than 2022.10.2 (e.g., 2022.10.1, 2022.09.x, earlier releases).
-
Confirm user creation is accessibleNavigate to Administration > Users > Create User account or verify the /admin/createUser.html endpoint responds. Check that the user creation functionality is not disabled via server configuration.Affected if User creation functionality is enabled and accessible to the actor performing the check.
-
Inspect existing user profile fields for malicious contentAccess Administration > Users and review each user's profile, particularly fields such as name, email, or other customizable profile attributes. Check for suspicious script tags, event handlers, or encoded payloads in these fields.Affected if Any user account contains JavaScript code or HTML in profile fields that could execute as XSS when viewed by other users or administrators.
You are affected if your TeamCity version is below 2022.10.2 and user creation functionality is enabled, or if you find malicious script content in existing user profile fields.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2022.10.2
Upgrade JetBrains TeamCity to version 2022.10.2 or later to patch the XSS vulnerability in the user creation process.
TeamCity 2022.10.2 or later
- Backup the existing TeamCity data directory and database
- Download TeamCity 2022.10.2 or later from the official JetBrains website
- Stop the running TeamCity server
- Extract and install the new version following the standard TeamCity upgrade procedure
- Start the TeamCity server and verify the upgrade was successful
- Confirm the user creation functionality works without XSS issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-48343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-48343 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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