CVE-2022-29927
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.04 reflected XSS on the Build Chain Status page 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 · moderate confidenceReflected cross-site scripting (XSS) vulnerability in JetBrains TeamCity's Build Chain Status page allows attackers to inject malicious scripts via unsanitized URL parameters. The vulnerability exists in versions prior to 2022.04 and is triggered when user-supplied input is reflected back in the page without proper encoding.
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.04CVSS 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.
-
Identify your TeamCity versionAccess the TeamCity Administration interface and navigate to the 'About' or 'Server Administration' section to view the installed version number, or check the startup logs for the version informationAffected if The version shown is earlier than 2022.04 (for example, 2022.03, 2021.x, or older)
-
Confirm the Build Chain Status page is accessibleNavigate to a project in TeamCity and access the Build Chain Status page, typically found under the Build Configuration settings or project overviewAffected if The page loads and displays build chain information in your TeamCity instance
-
Verify URL parameter reflectionAppend a test parameter to the Build Chain Status page URL (such as ?test=alert) and observe whether the value is reflected back in the page's HTML without encodingAffected if The parameter value appears unencoded in the rendered page source, indicating lack of input sanitization
-
Check for recent access logsReview TeamCity access logs for any suspicious requests to the Build Chain Status page with unusual URL parameters that may indicate exploitation attemptsAffected if Log entries show requests with script tags or javascript: URIs in URL parameters targeting the Build Chain Status endpoint
Your environment is affected if you are running TeamCity version earlier than 2022.04 and the Build Chain Status page is accessible, as the reflected XSS vulnerability exists in those versions.
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.04
Upgrade JetBrains TeamCity to version 2022.04 or later. Until upgrade is possible, implement URL parameter validation and output encoding on the Build Chain Status page.
TeamCity 2022.04 or later
- 1. Back up your TeamCity data directory and database before upgrading
- 2. Stop the TeamCity server
- 3. Download TeamCity 2022.04 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
- 4. Follow the official TeamCity upgrade instructions to install the new version
- 5. Start the TeamCity server
- 6. Verify the Build Chain Status page functions correctly and the XSS vulnerability is resolved
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-29927 — 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-29927 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