CVE-2017-4971: n/a Spring Web Flow vulnerability

CVE-2017-4971: An issue was discovered in Pivotal Spring Web Flow through 2.4.4.

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 14:47 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2017-4971 affects Spring Web Flow through 2.4.4 in a specific form-handling configuration. Some applications may accept malicious expression-language content during form submission when explicit binding mappings are absent. Business urgency depends on whether the organization still runs affected Spring Web Flow versions and vulnerable view-state patterns. Most likely exposure is legacy Java applications using Spring Web Flow through 2.4.4, especially form workflows with view states missing explicit binding mappings. Products and deployment scope are not identified in the bundle. Treat this as a legacy application exposure review. It is not KEV-listed in the provided bundle, but affected form workflows could be security-sensitive if still deployed. Mitigation focus: Inventory applications using Spring Web Flow through 2.4.4.; Check Pivotal or Spring advisory guidance for fixed versions and configuration changes.; Add explicit data-binding mappings for affected form-processing view states..

Prepared: Jun 13, 2026, 04:43 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-4971 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jun 13, 2017, 06:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://pivotal.io/security/cve-2017-4971CVE reference · x_refsource_CONFIRM
https://jira.spring.io/browse/SWF-1700CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/aSpring Web FlowSpring Web FlowListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.