{"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-8039 in the wild and no public exploit code.","fix":"Upgrade org.springframework.webflow:spring-webflow to 2.4.6 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2017-8039 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2017-8039 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.webflow:spring-webflow (Maven): affected all versions; fixed in 2.4.6\n- org.springframework.webflow:spring-webflow (Maven): affected all versions; fixed in 2.4.6\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-8039/ (Markdown: https://insights.sbomify.com/CVE-2017-8039/index.md)","id":"CVE-2017-8039","markdown":"https://insights.sbomify.com/CVE-2017-8039/index.md","name":"CVE-2017-8039","record":{"aliases":["GHSA-q4v9-qjmw-j7vf"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Spring Web Flow library","requires_auth":"none","summary":"Attackers can execute arbitrary code via malicious EL expressions in Spring Web Flow applications using default settings.","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.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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Insecure Default Initialization of Resource in Pivotal Spring Web Flow","id":"CVE-2017-8039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2017"},"n_packages":2,"n_references":2,"next":{"headline":"XML external entity in PCF Single Sign-On for PCF:1.3.x versions prior to 1.3.4, 1.4.x versions prior to 1.4.3","id":"CVE-2017-8040"},"packages":[{"ecosystem":"Maven","fixed":["2.4.6"],"introduced":["0"],"last_affected":[],"package":"org.springframework.webflow:spring-webflow","purl":null,"source":"GHSA-q4v9-qjmw-j7vf"},{"ecosystem":"Maven","fixed":["2.4.6"],"introduced":["0"],"last_affected":[],"package":"org.springframework.webflow:spring-webflow","purl":"pkg:maven/org.springframework.webflow/spring-webflow","source":"GHSA-q4v9-qjmw-j7vf"}],"prev":{"headline":"Missing authorization in Credhub Credhub-release version 1.1.0 only","id":"CVE-2017-8038"},"products":["Spring Web Flow Spring Web Flow 2.4.0 to 2.4.5 and Older unsupported versions are also affected"],"published":"2017-11-27","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-4971","kev_date_added":null,"published":"2017-06-13"},{"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via malicious EL expressions in Spring Web Flow applications using default settings.","url":"https://insights.sbomify.com/CVE-2017-8039/"}