First published: Tue Jun 13 2017(Updated: )
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.
Credit: security_alert@emc.com
Affected Software | Affected Version | How to fix |
---|---|---|
Pivotal Spring Web Flow | =2.4.0 | |
Pivotal Spring Web Flow | =2.4.1 | |
Pivotal Spring Web Flow | =2.4.2 | |
Pivotal Spring Web Flow | =2.4.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-4971 is classified as a medium severity vulnerability, primarily affecting the Pivotal Spring Web Flow framework.
To fix CVE-2017-4971, ensure that the value of the MvcViewFactoryCreator useSpringBinding property is explicitly set to true.
CVE-2017-4971 affects Pivotal Spring Web Flow versions 2.4.0, 2.4.1, 2.4.2, and 2.4.4.
CVE-2017-4971 is not exploitable in default configurations as the useSpringBinding property is disabled by default.
CVE-2017-4971 can lead to the execution of malicious EL expressions in view states during form submissions.