CVE-2017-4971 — spring-webflow
MEDIUMCVE-2017-4971 is a medium-severity (CVSS 5.9) CWE-1188 vulnerability in org.springframework.webflow:spring-webflow. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.springframework.webflow:spring-webflow — see the affected versions and patch details below.
Insecure Default Initialization of Resource in Pivotal Spring Web Flow
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.webflow:spring-webflowReal-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
An issue was discovered in Pivotal Spring Web Flow through 2.4.4. Applications that do not change the value of the MvcViewFactoryCreator useSpringBinding property which is disabled by default (i.e., set to 'false') can be vulnerable to malicious EL expressions in view states that process form submissions but do not have a sub-element to declare explicit data binding property mappings.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.webflow:spring-webflow | ≥ 2.4.0&&< 2.4.5 | 2.4.5org.springframework.webflow:spring-webflow:2.4.5 |
Affected Products
spring web flowbroadcomResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.webflow:spring-webflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.webflow:spring-webflow to 2.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-4971 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2017-4971 in your dependencies?
Find it across Maven, including transitive dependencies.