CVE-2017-8039
Insecure Default Initialization of Resource in Pivotal Spring Web Flow
An issue was discovered in Pivotal Spring Web Flow through 2.4.5. 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. NOTE: this issue exists because of an incomplete fix for CVE-2017-4971.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Exploit likelihood
What each source reports
NVD Score used
An issue was discovered in Pivotal Spring Web Flow through 2.4.5. 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. NOTE: this issue exists because of an incomplete fix for CVE-2017-4971.
- Record
CVE-2017-8039- CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - CVSS 2.0
- 4.3 Medium
AV:N/AC:M/Au:N/C:N/I:P/A:N - Weakness
- CWE-1188
- Updated
- 2026-11-02
CVE List No score
An issue was discovered in Pivotal Spring Web Flow through 2.4.5. 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. NOTE: this issue exists because of an incomplete fix for CVE-2017-4971.
- Record
CVE-2017-8039- Updated
- 2026-11-02
EUVDEUVD-2022-4886 No score
An issue was discovered in Pivotal Spring Web Flow through 2.4.5. 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. NOTE: this issue exists because of an incomplete fix for CVE-2017-4971.
- Record
EUVD-2022-4886- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-q4v9-qjmw-j7vf
Insecure Default Initialization of Resource in Pivotal Spring Web Flow
An issue was discovered in Pivotal Spring Web Flow through 2.4.5. 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. NOTE: this issue exists because of an incomplete fix for CVE-2017-4971.
- Record
GHSA-q4v9-qjmw-j7vf- CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - Weakness
- CWE-1188
- Updated
- 2026-11-02
OSV
An issue was discovered in Pivotal Spring Web Flow through 2.4.5. 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. NOTE: this issue exists because of an incomplete fix for CVE-2017-4971.
- Record
CVE-2017-8039- CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - Updated
- 2026-11-02
OSVGHSA-q4v9-qjmw-j7vf
Insecure Default Initialization of Resource in Pivotal Spring Web Flow
An issue was discovered in Pivotal Spring Web Flow through 2.4.5. 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. NOTE: this issue exists because of an incomplete fix for CVE-2017-4971.
- Record
GHSA-q4v9-qjmw-j7vf- CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - Weakness
- CWE-1188
- Updated
- 2026-11-02
OSVCLSA-2025-1760313983 No score
TuxCare security update for org.springframework.webflow:spring-webflow (2 CVEs)
TuxCare rebuilt org.springframework.webflow:spring-webflow to address 2 CVEs. Fixed in 2.3.3.RELEASE-tuxcare.1.
- Record
CLSA-2025-1760313983- Updated
- 2026-11-02
OSVCLSA-2025-1760313987 No score
TuxCare security update for org.springframework.webflow:spring-webflow (2 CVEs)
TuxCare rebuilt org.springframework.webflow:spring-webflow to address 2 CVEs. Fixed in 2.3.1.RELEASE-tuxcare.1.
- Record
CLSA-2025-1760313987- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
org.springframework.webflow:spring-webflowMaven |
through 2.4.5 | 2.4.6 |
org.springframework.webflow:spring-webflowTuxCare:Maven |
2.3.3.RELEASE up to 2.3.3.RELEASE-tuxcare.1 | 2.3.3.RELEASE-tuxcare.1 |
org.springframework.webflow:spring-webflowTuxCare:Maven |
2.3.1.RELEASE up to 2.3.1.RELEASE-tuxcare.1 | 2.3.1.RELEASE-tuxcare.1 |
org.springframework.webflow:spring-webflowMaven |
before 2.4.6, plus listed versions 2.0.6.RELEASE2.0.7.RELEASE2.0.8.RELEASE2.0.9.RELEASE2.1.0.RELEASE Show 13 moreShow less2.1.1.RELEASE2.2.0.RELEASE2.2.1.RELEASE2.3.0.RELEASE2.3.1.RELEASE2.3.2.RELEASE2.3.3.RELEASE2.3.4.RELEASE2.4.0.RELEASE2.4.1.RELEASE2.4.2.RELEASE2.4.4.RELEASE2.4.5.RELEASE |
2.4.6 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2017-8039 is a medium vulnerability (CVSS 5.9) in Broadcom Spring Web Flow, published November 27, 2017. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.13%, the 66th percentile. Fixed in org.springframework.webflow:spring-webflow 2.4.6.