# CVE-2024-22262: CVE-2024-22262: Spring Framework URL Parsing with Host Validation

> Attackers can bypass host validation in UriComponentsBuilder to perform SSRF or open redirect attacks, impacting applications using this library.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Apr 2024
- **Updated:** 13 Feb 2025
- **Also known as:** CLSA-2026-1782781162, DEBIAN-CVE-2024-22262, ECHO-f8ed-8dc1-2115, GHSA-2wrp-6fg6-hmc5, ROOT-APP-MAVEN-CVE-2024-22262, UBUNTU-CVE-2024-22262

## What is CVE-2024-22262?

CVE-2024-22262 is a high-severity server-side request forgery vulnerability in Spring Framework, published on 16 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2024-22262?

6 open source packages ship an affected version, including org.springframework:spring-web.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework:spring-web` | Maven | All versions | 5.3.34 |
| `org.springframework:spring-web` | Maven | All versions | 5.3.34 |
| `org.springframework:spring-web` | Maven | From 6.0.0 | 6.0.19 |
| `org.springframework:spring-web` | Maven | From 6.0.0 | 6.0.19 |
| `org.springframework:spring-web` | Maven | From 6.1.0 | 6.1.6 |
| `org.springframework:spring-web` | Maven | From 6.1.0 | 6.1.6 |

## How do I fix CVE-2024-22262?

Upgrade org.springframework:spring-web to a fixed version for your release line: 5.3.34, 6.0.19 or 6.1.6.

## Is CVE-2024-22262 being exploited?

There is no known exploitation of CVE-2024-22262 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Performant-Labs/CVE-2024-22262 (github_poc): https://github.com/Performant-Labs/CVE-2024-22262

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22262 and fix it if it is affected.

What it is: CVE-2024-22262 is a high-severity server-side request forgery vulnerability in Spring Framework, published on 16 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-22262 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework:spring-web (Maven): affected all versions; fixed in 5.3.34
- org.springframework:spring-web (Maven): affected all versions; fixed in 5.3.34
- org.springframework:spring-web (Maven): affected from 6.0.0; fixed in 6.0.19
- org.springframework:spring-web (Maven): affected from 6.0.0; fixed in 6.0.19
- org.springframework:spring-web (Maven): affected from 6.1.0; fixed in 6.1.6
- org.springframework:spring-web (Maven): affected from 6.1.0; fixed in 6.1.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-22262/ (Markdown: https://insights.sbomify.com/CVE-2024-22262/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-22262
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-22262
- OSV: https://osv.dev/vulnerability/CVE-2024-22262

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-22262/
Summaries are generated and may contain mistakes; the official description above is the record.