CVE-2022-24333
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, blind SSRF via an XML-RPC call 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 · high confidenceA blind Server-Side Request Forgery (SSRF) vulnerability in JetBrains TeamCity versions before 2021.2 allows attackers to make the server perform arbitrary HTTP requests via XML-RPC API calls without viewing the full response. This could enable internal network reconnaissance or attacks against internal services.
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.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed TeamCity versionAccess the TeamCity administration web interface and navigate to 'Administration' > 'Server Administration' > 'Server Information', or check the <TeamCity home>/buildAgent/logs/teamcity-startup.log file for the version string.Affected if The version displayed is lower than 2021.2 (for example, 2021.1.x, 2020.x, or earlier)
-
Verify XML-RPC API endpoint availabilityAttempt to access the XML-RPC API endpoint at /xmlrpc or /rpc/xmlrpc by making an HTTP request to your TeamCity server URL.Affected if The endpoint responds with HTTP 200 or returns XML-RPC method listings, indicating the API is enabled and reachable
-
Confirm XML-RPC is not restricted by network controlsReview TeamCity server firewall rules, reverse proxy configuration, or TeamCity's internal access control settings to determine if the /xmlrpc endpoint is exposed to untrusted networks or the public internet.Affected if The XML-RPC API is accessible from networks outside the trusted internal environment
Your environment is affected if the installed TeamCity version is below 2021.2 AND the XML-RPC API endpoint is accessible to attackers.
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
Upgrade JetBrains TeamCity to version 2021.2 or later. If immediate upgrade is not feasible, restrict XML-RPC API access to trusted networks only.
2021.2
- Back up your TeamCity data, configuration, and database before upgrading
- Download TeamCity 2021.2 or later from the official JetBrains website (https://www.jetbrains.com/teamcity/download/)
- Stop the TeamCity server
- Follow the official TeamCity upgrade instructions to install the new version
- Start the upgraded TeamCity server and verify all services are running correctly
- Test critical build configurations to ensure functionality is preserved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24333 — 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-24333 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