Every CVE Search/ Get API key

CVE-2017-4971

Insecure Default Initialization of Resource in Pivotal Spring Web Flow

5.9 MediumPublic exploitFix available

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.

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

14.7%Up 13.8 points since Apr 14, 2021
90%50%10%1%

What each source reports

NVD Score used 5.9

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.

Record
CVE-2017-4971
CVSS 3.0
5.9 MediumCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
CVSS 2.0
4.3 MediumAV: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.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.

Record
CVE-2017-4971
Updated
2026-11-02
EUVDEUVD-2022-3775 No score

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.

Record
EUVD-2022-3775
Updated
2026-11-03
GitHub AdvisoriesGHSA-fg9w-cffm-pmh2 5.9

Insecure Default Initialization of Resource in Pivotal Spring Web Flow

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.

Record
GHSA-fg9w-cffm-pmh2
CVSS 3.0
5.9 MediumCVSS: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 5.9

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.

Record
CVE-2017-4971
CVSS 3.0
5.9 MediumCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Updated
2026-11-02
OSVGHSA-fg9w-cffm-pmh2 5.9

Insecure Default Initialization of Resource in Pivotal Spring Web Flow

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.

Record
GHSA-fg9w-cffm-pmh2
CVSS 3.0
5.9 MediumCVSS: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

Affected packages
PackageAffectedFixed
org.springframework.webflow:spring-webflow
Maven
2.4.0 to 2.4.4
2.4.5
org.springframework.webflow:spring-webflow
TuxCare:Maven
2.3.3.RELEASE up to 2.3.3.RELEASE-tuxcare.1
2.3.3.RELEASE-tuxcare.1
org.springframework.webflow:spring-webflow
TuxCare:Maven
2.3.1.RELEASE up to 2.3.1.RELEASE-tuxcare.1
2.3.1.RELEASE-tuxcare.1
org.springframework.webflow:spring-webflow
Maven
2.4.0 up to 2.4.5, plus listed versions
2.4.0.RELEASE2.4.1.RELEASE2.4.2.RELEASE2.4.4.RELEASE
2.4.5

Public exploits

Links only. Every CVE stores no exploit code.

Public exploits
SourceLinkDate
PoC in GitHubcved-sources/cve-2017-49712019-01-17

History

History
RecordedChangedSources
aliasesEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV, PoC in GitHub

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2017-4971 is a medium vulnerability (CVSS 5.9) in Broadcom Spring Web Flow, published June 13, 2017. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 14.7%, the 96th percentile. Fixed in org.springframework.webflow:spring-webflow 2.4.5.

References

MoveEnter Open