{"answers":{"affected":"2 open source packages ship an affected version, including org.springframework.webflow:spring-webflow. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-4971 in the wild and no public exploit code.","fix":"Upgrade org.springframework.webflow:spring-webflow to 2.4.5 or later.","what":"CVE-2017-4971 is a medium-severity code injection vulnerability in Spring Web Flow, published on 13 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-4971 and fix it if it is affected.\n\nWhat it is: CVE-2017-4971 is a medium-severity code injection vulnerability in Spring Web Flow, published on 13 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-4971 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.webflow:spring-webflow (Maven): affected from 2.4.0; fixed in 2.4.5\n- org.springframework.webflow:spring-webflow (Maven): affected from 2.4.0; fixed in 2.4.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-4971/ (Markdown: https://insights.sbomify.com/CVE-2017-4971/index.md)","id":"CVE-2017-4971","markdown":"https://insights.sbomify.com/CVE-2017-4971/index.md","name":"CVE-2017-4971","record":{"aliases":["GHSA-fg9w-cffm-pmh2"],"analysis":{"component_type":"library","fix_type":"configuration_change","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Spring Web Flow library","requires_auth":"none","summary":"Attackers can execute malicious code via EL expressions in Spring Web Flow if Spring binding is explicitly enabled without proper data binding mappings.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"spring_web_flow","vendor":"broadcom"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2019-01-17","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-01-17T17:31:59Z","kind":"github_poc","ref":"https://github.com/cved-sources/cve-2017-4971","stars":0,"title":"cve-2017-4971"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Insecure Default Initialization of Resource in Pivotal Spring Web Flow","id":"CVE-2017-4971","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2017"},"n_packages":2,"n_references":3,"next":{"headline":"SQL injection in Cloud Foundry UAA","id":"CVE-2017-4972"},"packages":[{"ecosystem":"Maven","fixed":["2.4.5"],"introduced":["2.4.0"],"last_affected":[],"package":"org.springframework.webflow:spring-webflow","purl":null,"source":"GHSA-fg9w-cffm-pmh2"},{"ecosystem":"Maven","fixed":["2.4.5"],"introduced":["2.4.0"],"last_affected":[],"package":"org.springframework.webflow:spring-webflow","purl":"pkg:maven/org.springframework.webflow/spring-webflow","source":"GHSA-fg9w-cffm-pmh2"}],"prev":{"headline":"Auth bypass in Cloud Foundry","id":"CVE-2017-4970"},"products":["Spring Web Flow"],"published":"2017-06-13","related":[{"cvss_score":6.4,"headline":"Data Binding Vulnerability in Spring Web Flow with Unified EL Parser","id":"CVE-2026-40985","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":5.9,"headline":"Insecure Default Initialization of Resource in Pivotal Spring Web Flow","id":"CVE-2017-8039","kev_date_added":null,"published":"2017-11-27"},{"cvss_score":4.8,"headline":"Spring Web Flow JS RemotingHandler renders non-HTML Response as HTML","id":"CVE-2026-40986","kev_date_added":null,"published":"2026-06-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can execute malicious code via EL expressions in Spring Web Flow if Spring binding is explicitly enabled without proper data binding mappings.","url":"https://insights.sbomify.com/CVE-2017-4971/"}