CVE-2022-29929
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 potential XSS via Referrer header 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 confidenceCross-site scripting (XSS) vulnerability in JetBrains TeamCity where the HTTP Referrer header is not properly sanitized before being used or displayed, allowing injection of malicious scripts.
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.
-
Check TeamCity server versionAccess the TeamCity web interface and navigate to the Administration > Server Configuration page, or check the version.txt file in the TeamCity installation directory if you have direct server accessAffected if The installed version is any release prior to 2022.04 (for example, 2022.03.x, 2021.x, or earlier)
-
Confirm TeamCity web interface is accessibleVerify that the TeamCity web server is running and reachable at your configured URL (typically port 8111 by default)Affected if The web interface is accessible to users or attackers over HTTP/HTTPS - this is required for the Referrer header to be processed and potentially reflected back
-
Identify any areas where HTTP headers are logged or displayedReview server logs, build run logs, or any custom plugins that might capture or display the HTTP Referrer header valueAffected if Any functionality exists that logs, displays, or processes the Referrer header from incoming requests without sanitization - the vulnerability exists in the core product regardless of whether specific header-display features are intentionally used
You are affected if your TeamCity installation version is any build earlier than 2022.04 and the web interface is accessible, since the improper Referrer header sanitization exists in the core server code.
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 to TeamCity version 2022.04 or later which contains the fix for proper Referrer header sanitization.
TeamCity 2022.04 or later
- Back up your TeamCity data directory (usually <TeamCity Home>/data) before upgrading
- Download TeamCity 2022.04 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
- Stop the TeamCity server service
- Run the TeamCity installer for the new version, pointing to the existing TeamCity installation directory
- Follow the on-screen upgrade prompts - the installer will detect the existing installation and upgrade it
- Start the TeamCity server service after upgrade completes
- Verify the server is running and accessible, and check that the Referrer header XSS vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29929 — 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-29929 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