CVE-2017-8039: Medium severity Pivotal Spring Web Flow vulnerability

Published Nov 27, 2017
·
Updated

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.

Affected Software

10 affected components
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
Pivotal Spring Web Flow=2.4.5
Broadcom Spring Web Flow=2.4.0
Broadcom Spring Web Flow=2.4.1
Broadcom Spring Web Flow=2.4.2
Broadcom Spring Web Flow=2.4.4
Broadcom Spring Web Flow=2.4.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Enable the MvcViewFactoryCreator useSpringBinding property (set to 'true') to prevent vulnerability to malicious EL expressions in view states that process form submissions without explicit data binding mappings. The property is disabled by default ('false').

    Pivotal Spring Web Flow (MvcViewFactoryCreator) useSpringBinding = true
  2. Compensating control

    For applications that do not use/require the MvcViewFactoryCreator useSpringBinding behavior, ensure view states processing form submissions have explicit data binding property mappings (i.e., include a sub-element that declares explicit data binding property mappings) so they do not rely on the default disabled useSpringBinding.

Event History

Nov 27, 2017
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
DescriptionWeakness
Data Sourced
via NVD·10:29 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is CVE-2017-8039?

CVE-2017-8039 is a vulnerability in Pivotal Spring Web Flow through version 2.4.5 that allows malicious EL expressions in view states processing form submissions.

2

How does CVE-2017-8039 affect Pivotal Spring Web Flow?

CVE-2017-8039 affects Pivotal Spring Web Flow versions 2.4.0, 2.4.1, 2.4.2, 2.4.4, and 2.4.5.

3

What is the severity level of CVE-2017-8039?

The severity level of CVE-2017-8039 is medium, with a CVSS score of 5.9.

4

How can I fix CVE-2017-8039?

To fix CVE-2017-8039, make sure to update Pivotal Spring Web Flow to version 2.4.6 or later.

5

Where can I find more information about CVE-2017-8039?

More information about CVE-2017-8039 can be found at the following references: http://www.securityfocus.com/bid/100849 and https://pivotal.io/security/cve-2017-8039.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203