{"answers":{"affected":"4 open source packages ship an affected version, including org.apache.struts:struts2-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-4436 in the wild and no public exploit code.","fix":"Upgrade org.apache.struts:struts2-core to a fixed version for your release line: 2.3.29 or 2.5.1.","what":"CVE-2016-4436 is a critical vulnerability in Apache Struts, published on 3 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-4436 and fix it if it is affected.\n\nWhat it is: CVE-2016-4436 is a critical vulnerability in Apache Struts, published on 3 Oct 2016. 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-2016-4436 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.struts:struts2-core (Maven): affected from 2.0.0; fixed in 2.3.29\n- org.apache.struts:struts2-core (Maven): affected from 2.0.0; fixed in 2.3.29\n- org.apache.struts:struts2-core (Maven): affected from 2.5-BETA1; fixed in 2.5.1\n- org.apache.struts:struts2-core (Maven): affected from 2.5-BETA1; fixed in 2.5.1\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-2016-4436/ (Markdown: https://insights.sbomify.com/CVE-2016-4436/index.md)","id":"CVE-2016-4436","markdown":"https://insights.sbomify.com/CVE-2016-4436/index.md","name":"CVE-2016-4436","record":{"aliases":["GHSA-xm92-v2mq-842q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Java web framework","requires_auth":"none","summary":"Attackers can exploit improper action name cleanup in Apache Struts 2, potentially leading to unspecified security impacts.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"struts","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"Apache Struts 2 before 2.3.29 and 2.5.x before 2.5.1 allow attackers to have unspecified impact via vectors related to improper action name clean up.","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":"Apache Struts improper action name cleanup","id":"CVE-2016-4436","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:struts","products":["apache:struts"],"type":"other","year":"2016"},"n_packages":4,"n_references":5,"next":{"headline":"Apache Shiro Code Execution","id":"CVE-2016-4437"},"packages":[{"ecosystem":"Maven","fixed":["2.3.29"],"introduced":["2.0.0"],"last_affected":[],"package":"org.apache.struts:struts2-core","purl":null,"source":"GHSA-xm92-v2mq-842q"},{"ecosystem":"Maven","fixed":["2.3.29"],"introduced":["2.0.0"],"last_affected":[],"package":"org.apache.struts:struts2-core","purl":"pkg:maven/org.apache.struts/struts2-core","source":"GHSA-xm92-v2mq-842q"},{"ecosystem":"Maven","fixed":["2.5.1"],"introduced":["2.5-BETA1"],"last_affected":[],"package":"org.apache.struts:struts2-core","purl":null,"source":"GHSA-xm92-v2mq-842q"},{"ecosystem":"Maven","fixed":["2.5.1"],"introduced":["2.5-BETA1"],"last_affected":[],"package":"org.apache.struts:struts2-core","purl":"pkg:maven/org.apache.struts/struts2-core","source":"GHSA-xm92-v2mq-842q"}],"prev":{"headline":"Missing authorization in Cloud Foundry","id":"CVE-2016-4435"},"products":["n/a"],"published":"2016-10-03","related":[{"cvss_score":9.8,"headline":"Apache Struts Remote Code Execution","id":"CVE-2020-17530","kev_date_added":"2021-11-03","published":"2020-12-11"},{"cvss_score":9.8,"headline":"Apache Struts 1 Improper Input Validation","id":"CVE-2017-9791","kev_date_added":"2022-02-10","published":"2017-07-10"},{"cvss_score":9.8,"headline":"Apache Struts Remote Code Execution","id":"CVE-2017-5638","kev_date_added":"2021-11-03","published":"2017-03-11"},{"cvss_score":9.8,"headline":"Apache Struts 2 Improper Input Validation","id":"CVE-2012-0391","kev_date_added":"2022-01-21","published":"2012-01-08"},{"cvss_score":8.1,"headline":"Apache Struts Remote Code Execution","id":"CVE-2018-11776","kev_date_added":"2021-11-03","published":"2018-08-22"},{"cvss_score":8.1,"headline":"Apache Struts Deserialization of Untrusted Data","id":"CVE-2017-9805","kev_date_added":"2021-11-03","published":"2017-09-15"},{"cvss_score":8.1,"headline":"Apache Struts Command Injection","id":"CVE-2016-3081","kev_date_added":"2026-10-08","published":"2016-04-26"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Attackers can exploit improper action name cleanup in Apache Struts 2, potentially leading to unspecified security impacts.","url":"https://insights.sbomify.com/CVE-2016-4436/"}