CVE-2022-24342
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 2021.2.1, URL injection leading to CSRF 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 confidenceIn JetBrains TeamCity before version 2021.2.1, an attacker could potentially exploit a URL injection vulnerability to perform Cross-Site Request Forgery (CSRF) attacks. This could allow an authenticated user to be tricked into executing unintended actions on the TeamCity server.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Locate TeamCity version numberOpen the TeamCity web interface and view the version displayed on the login page or navigate to Administration > Server Administration > Server Configuration to see the installed version numberAffected if The displayed version is any release prior to 2021.2.1 (for example, 2021.2.0, 2021.1.x, 2021.0.x, or earlier)
-
Confirm exact version via API or logsSend a GET request to the TeamCity REST API endpoint /app/rest/server/version or check the teamcity-server.log file in the logs directory for the version stringAffected if The returned version string or log entry shows a version lower than 2021.2.1
-
Verify patch statusCheck if any manual patches or hotfixes have been applied to the TeamCity installation by reviewing the installation directory for patch files or consulting server documentationAffected if No patches have been applied and the base version remains below 2021.2.1
If the installed TeamCity version is 2021.2.1 or later, the environment is not affected by this CVE; any version below 2021.2.1 is potentially vulnerable to the URL injection/CSRF issue.
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 remediate this vulnerability.
2021.2.1 or later
- Create a full backup of the TeamCity data directory and database
- Stop the TeamCity server
- Download TeamCity 2021.2.1 or a later stable version from the official JetBrains website
- Run the installer or apply the upgrade package to your existing TeamCity installation
- Verify the upgrade completed successfully
- Start the TeamCity server
- Confirm the server is operational and accessible
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-24342 — 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-24342 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