dbcve.org
Open RedirectWeakness · CWE-601

CVE-2024-22262

HIGH · 8.1 CVSS v3.1 Published 2024-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Applications 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. This is the same as CVE-2024-22259 https://spring.io/security/cve-2024-22259  and CVE-2024-22243 https://spring.io/security/cve-2024-22243 , but with different input.

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 confidence

UriComponentsBuilder in Spring Framework fails to properly sanitize URLs when parsing externally provided input (e.g., from query parameters). An attacker can craft malicious URLs that bypass host validation checks, leading to open redirect (CWE-601) or SSRF attacks. This is the same root cause as CVE-2024-22259 and CVE-2024-22243 but with different input vectors.

MitigationUpgrade to Spring Framework 6.1.4+ or 5.3.32+ and review all code paths using UriComponentsBuilder with untrusted input to ensure host validation cannot be bypassed.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Spring Framework version in use
    Check your project's dependency management (Maven pom.xml, Gradle build.gradle, or the spring-core JAR manifest). Run: mvn dependency:tree | grep spring-core or examine the spring-core-*.jar META-INF/MANIFEST.MF file.
    Affected if The version is 5.3.x before 5.3.32, or 6.x before 6.1.4, or if the version cannot be determined but the library is present.
  2. Locate code using UriComponentsBuilder with external input
    Search your codebase for usages of org.springframework.web.util.UriComponentsBuilder, specifically where parse() or fromUri() methods are called with query parameters, request parameters, or any user-supplied string. Search: UriComponentsBuilder.parse( and UriComponentsBuilder.fromUri(
    Affected if UriComponentsBuilder parses URLs derived from query parameters, request parameters, headers, or other untrusted sources without subsequent host validation.
  3. Check for host validation after parsing external URLs
    Review code that passes external input to UriComponentsBuilder and verify whether getHost() is called afterward to validate the parsed host against an allowlist or blocklist, or whether the UriComponents is used directly in redirects or HTTP requests.
    Affected if The parsed UriComponents is used directly in HTTP requests, redirects, or template rendering without calling getHost() to validate the domain.
  4. Identify SSRF and open redirect sinks
    Search for patterns where the parsed UriComponents or its host/scheme is passed to RestTemplate, WebClient, redirect methods (sendRedirect), or template engines (Thymeleaf, Freemarker) without validation.
    Affected if The code performs HTTP calls or redirects using the unvalidated URI without verifying the host belongs to an expected domain.
  5. Review request parameter propagation to UriComponentsBuilder
    Check controller methods that receive @RequestParam, @RequestBody, or @CookieValue and pass these values to UriComponentsBuilder without sanitization, especially in URL construction or redirection logic.
    Affected if Controller parameters are directly passed to UriComponentsBuilder.parse() or fromUri() and used without host validation.

You are affected if your Spring Framework version is below 5.3.32 or 6.1.4 AND your code uses UriComponentsBuilder to parse externally provided URLs without validating the parsed host before use in HTTP requests or redirects.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Spring Framework 6.1.4+ or 5.3.32+ and review all code paths using UriComponentsBuilder with untrusted input to ensure host validation cannot be bypassed.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22262 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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