CVE-2024-22243
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 · uneditedApplications that use UriComponentsBuilder to parse an externally provided URL (e.g. through a query parameter) AND perform validation checks on the host of the parsed URL may be vulnerable to a open redirect https://cwe.mitre.org/data/definitions/601.html attack or to a SSRF attack if the URL is used after passing validation checks.
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 confidenceUriComponentsBuilder in Spring Framework can produce URLs that bypass host validation checks, allowing crafted URLs to pass validation but then redirect to arbitrary hosts (open redirect) or make requests to internal services (SSRF). This occurs because UriComponentsBuilder may reconstruct URLs differently than the original input, creating a parsing discrepancy that bypasses validation logic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 Spring Framework usageLocate Spring Framework libraries in your project dependencies (e.g., spring-core, spring-web, spring-framework). Check build files (pom.xml, build.gradle) or application libraries for Spring dependencies.Affected if Spring Framework is present in the application
-
Check Spring Framework versionDetermine the installed Spring Framework version from your dependency management (Maven/Gradle) or libraries. Compare it to the patched version (6.0.x and 5.3.x series have the fix).Affected if The Spring Framework version is lower than the patched version and falls within the affected range
-
Identify UriComponentsBuilder usageSearch source code for usage of org.springframework.web.util.UriComponentsBuilder, particularly where it parses URLs from external or user-controlled input.Affected if UriComponentsBuilder is used to process URLs from untrusted sources
-
Check for URL validation after parsingExamine code that uses UriComponentsBuilder to see if host validation is performed on the reconstructed URL object rather than validating the original URL string before parsing.Affected if Validation is applied to the UriComponents/UriTemplate object AFTER parsing rather than to the original input string BEFORE parsing (this is the vulnerable pattern)
-
Review redirect and request logicAudit any code paths that use parsed URLs for redirects, HTTP requests, or forwarding to determine if they accept arbitrary host values.Affected if Application performs redirects or makes HTTP requests using URLs parsed by UriComponentsBuilder without additional host allow-listing
Your environment is affected if you use a vulnerable Spring Framework version AND your code validates reconstructed URL objects from UriComponentsBuilder rather than validating the original URL string before parsing.
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.
From vendor dataUpdate Spring Framework to the patched version. Additionally, validate the original URL string BEFORE parsing with UriComponentsBuilder rather than validating the reconstructed URL object.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22243 — 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-2024-22243 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