CVE-2022-24339
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 · uneditedJetBrains TeamCity before 2021.2.1 was vulnerable to stored XSS.
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 confidenceJetBrains TeamCity before version 2021.2.1 contained a stored XSS vulnerability that allowed authenticated users to inject malicious scripts into application fields, which would then be executed in the browsers of other users viewing that content.
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< 2021.2.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed TeamCity versionAccess the TeamCity web interface and check the version number displayed in the footer of any page, or navigate to Administration > Global Settings to view the version informationAffected if The displayed version is any build before 2021.2.1 (e.g., 2021.2.0, 2021.1.x, 2020.x.x, or earlier)
-
Confirm version from startup logsExamine the TeamCity server startup logs (typically found in <TeamCity_HOME>/logs/ directory) for a line containing 'TeamCity version' or similar version identifierAffected if The logged version indicates a build number lower than 2021.2.1
-
Verify TeamCity authentication is enabledCheck that the TeamCity server has user authentication enabled and is accessible to authenticated users (not in read-only mode or completely locked down)Affected if Users can log in to TeamCity with valid credentials
-
Confirm user-accessible input fields existIdentify any active TeamCity fields where authenticated users can submit or modify data, such as project descriptions, build configurations, user profiles, or VCS commit messages displayed in the UIAffected if Any application fields accept user input that is rendered and displayed to other users in the web interface
If the installed TeamCity version is any release before 2021.2.1 and the server is accessible to authenticated users with input fields, the environment is vulnerable to stored XSS via CVE-2022-24339.
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 · scoped2021.2.1
Upgrade TeamCity to version 2021.2.1 or later to patch the stored XSS vulnerability.
TeamCity 2021.2.1
- Confirm current TeamCity version is below 2021.2.1 by checking the server UI or using the /app/rest/server/version endpoint
- Review the official JetBrains TeamCity upgrade documentation at https://www.jetbrains.com/help/teamcity/upgrade.html
- Create a complete backup of the TeamCity data directory, database, and configuration files
- Stop the TeamCity server
- Install TeamCity version 2021.2.1 or later
- Start the TeamCity server and verify all services are running
- Test that the stored XSS vulnerability is no longer present by verifying user input is properly sanitized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24339 — 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-24339 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