CVE-2017-8039 Insecure Default Initialization of Resource in Pivotal Spring Web Flow

Medium 5.9 Published 27 Nov 2017 Updated 5 Aug 2024

Attackers can execute arbitrary code via malicious EL expressions in Spring Web Flow applications using default settings.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2017-8039?

CVE-2017-8039 is a medium-severity code injection vulnerability in Spring Web Flow Spring Web Flow 2.4.0 to 2.4.5 and Older unsupported versions are also affected, published on 27 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-1188

Which versions are affected by CVE-2017-8039?

2 open source packages ship an affected version, including org.springframework.webflow:spring-webflow. It affects 1 product.

Package	Affected	Fixed in
`org.springframework.webflow:spring-webflow` Maven	All versions	`2.4.6`
`org.springframework.webflow:spring-webflow` Maven	All versions	`2.4.6`

Products include Broadcom Spring Web Flow.

How do I fix CVE-2017-8039?

Upgrade org.springframework.webflow:spring-webflow to 2.4.6 or later.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2017-8039 being exploited?

There is no known exploitation of CVE-2017-8039 in the wild and no public exploit code.

Sources

Also known as GHSA-q4v9-qjmw-j7vf.