Spring FrameworkFramework / library · VMware

CVE-2024-22259

HIGH · 8.1 CVSS v3.1 Published 2024-03-16
Fix available
A fix is available. Upgrade to 5.3.33 / 6.0.18 or later.
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 in Spring Framework 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-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

Applications using UriComponentsBuilder in Spring Framework to parse externally-provided URLs (e.g., from query parameters) and perform host validation checks are vulnerable to open redirect or SSRF attacks due to a validation bypass. The parser can be tricked into passing validation checks but then resolving to a different host when the URL is used, similar to CVE-2024-22243 but with different input vectors.

MitigationUpgrade Spring Framework to the latest patched version and review all code paths using UriComponentsBuilder with external input to ensure host validation cannot be bypassed. Consider using stricter validation that checks the final resolved host rather than the parsed host.

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
Spring FrameworkFramework / library
Affected:< 5.3.33>= 6.0.0, < 6.0.18>= 6.1.0, < 6.1.5
Active Iq Unified ManagerApplication
Affected:all versions

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 Spring Framework version
    Check your project dependencies (pom.xml, build.gradle, or manifest files) for the spring-core or spring-web version. Run 'mvn dependency:tree | grep spring' or 'gradle dependencies | grep spring'
    Affected if The installed version is < 5.3.33, or >= 6.0.0 and < 6.0.18, or >= 6.1.0 and < 6.1.5
  2. Locate UriComponentsBuilder usage with external input
    Search codebase for 'UriComponentsBuilder' and trace whether the input comes from external sources such as query parameters, request parameters, headers, or user-controlled data. Search: grep -r 'UriComponentsBuilder' --include='*.java'
    Affected if UriComponentsBuilder parses URLs derived from external/unsanitized input
  3. Verify host validation logic exists after parsing
    Review code paths that use UriComponentsBuilder to parse external URLs. Look for host validation logic (e.g., host comparison, allowlist checks) applied to the parsed UriComponents before use
    Affected if Host validation is performed on the parsed UriComponents but does not verify the final resolved host
  4. Check for SSRF/open redirect patterns
    Audit any network calls or redirects made using URLs parsed by UriComponentsBuilder from external input. Look for patterns where the host is checked but the URL is later used as-is
    Affected if URLs from UriComponentsBuilder are used in HTTP calls or redirects without re-validating the final host
  5. Identify NetApp Active IQ Unified Manager installation
    Check if NetApp Active IQ Unified Manager is installed. Look for installation directories, running services, or product documentation
    Affected if NetApp Active IQ Unified Manager is running (all versions are affected)

You are affected if your Spring Framework version is within the vulnerable ranges AND UriComponentsBuilder is used to parse externally-provided URLs with host validation that can be bypassed.

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
Upgrade available Upgrade to 5.3.33 / 6.0.18 / 6.1.5 or later
Fixed in 5.3.336.0.186.1.5
Interim mitigation

Upgrade Spring Framework to the latest patched version and review all code paths using UriComponentsBuilder with external input to ensure host validation cannot be bypassed. Consider using stricter validation that checks the final resolved host rather than the parsed host.

Fix this in Spring Framework Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22259 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22259 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