Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1494413 - (CVE-2017-8039) CVE-2017-8039 spring-webflow: Data Binding Expression Vulnerability in Spring Web Flow
CVE-2017-8039 spring-webflow: Data Binding Expression Vulnerability in Spring...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20170915,repor...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-22 04:33 EDT by Adam Mariš
Modified: 2017-09-22 04:38 EDT (History)
13 users (show)

See Also:
Fixed In Version: spring-webflow 2.4.6
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-09-22 04:38:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2017-09-22 04:33:51 EDT
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.

This CVE addresses a second path to exploiting the same vulnerability as the one described under CVE-2017-4971.

External References:

https://pivotal.io/security/cve-2017-8039
Comment 1 Adam Mariš 2017-09-22 04:37:33 EDT
Statement:

This issue affects the versions of spring-webflow as shipped with Red Hat Enterprise Virtualization 3. Red Hat Product Security has rated this issue as having (Low|Moderate) security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Note You need to log in before you can comment on or make changes to this bug.