GHSA-2wrp-6fg6-hmc5 — spring-web
HIGHGHSA-2wrp-6fg6-hmc5 is a high-severity (CVSS 8.1) Open Redirect vulnerability in org.springframework:spring-web. A fix is available for org.springframework:spring-web — see the affected versions and patch details below.
Spring Framework URL Parsing with Host Validation
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2wrp-6fg6-hmc5.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-2wrp-6fg6-hmc5 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.springframework:spring-web☕org.springframework:spring-web☕org.springframework:spring-webReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-web | all versions | 5.3.34org.springframework:spring-web:5.3.34 |
| ☕Maven | org.springframework:spring-web | ≥ 6.0.0&&< 6.0.19 | 6.0.19org.springframework:spring-web:6.0.19 |
| ☕Maven | org.springframework:spring-web | ≥ 6.1.0&&< 6.1.6 | 6.1.6org.springframework:spring-web:6.1.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-web to 5.3.34 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2wrp-6fg6-hmc5 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2wrp-6fg6-hmc5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2wrp-6fg6-hmc5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat Fuse 7 does not use the affected function, but the function is still available for user convenience which demands one to validate the input.
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for GHSA-2wrp-6fg6-hmc5 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Apache Camel 3.20.6 for Spring Boot | springframework | RHSA-2024:3708 |
Frequently Asked Questions
Is GHSA-2wrp-6fg6-hmc5 in your dependencies?
O3 Security finds GHSA-2wrp-6fg6-hmc5 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.