{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2016-8673 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-8673 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-8673 is a high-severity vulnerability in n/a, published on 23 Nov 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2016-8673 and fix it if it is affected.\n\nWhat it is: CVE-2016-8673 is a high-severity vulnerability in n/a, published on 23 Nov 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2016-8673 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-8673/ (Markdown: https://insights.sbomify.com/CVE-2016-8673/index.md)","id":"CVE-2016-8673","markdown":"https://insights.sbomify.com/CVE-2016-8673/index.md","name":"CVE-2016-8673","record":{"aliases":["GHSA-4v5h-4j58-whhg"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Siemens SIMATIC PLC","requires_auth":"none","summary":"Remote attackers can perform actions with authenticated user permissions via CSRF on the integrated web server of affected SIMATIC devices.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"simatic_cp_343-1_firmware","vendor":"siemens"},{"product":"simatic_cp_443-1_firmware","vendor":"siemens"},{"product":"simatic_s7_300_cpu_firmware","vendor":"siemens"},{"product":"simatic_s7_400_cpu_firmware","vendor":"siemens"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A vulnerability has been identified in SIMATIC CP 343-1 Advanced (incl. SIPLUS NET variant) (All versions \u003c V3.0.53), SIMATIC CP 443-1 Advanced (incl. SIPLUS NET variant) (All versions \u003c V3.2.17), SIMATIC S7-300 PN/DP CPU family (incl. SIPLUS variants) (All versions), SIMATIC S7-400 PN/DP CPU family (incl. SIPLUS variants) (All versions). The integrated web server at port 80/TCP or port 443/TCP of the affected devices could allow remote attackers to perform actions with the permissions of an authenticated user, provided the targeted user has an active session and is induced to trigger the malicious request.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site request forgery in n/a","id":"CVE-2016-8673","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2016"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in n/a","id":"CVE-2016-8674"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2016-8672"},"products":["n/a"],"published":"2016-11-23","related":[{"cvss_score":9.7,"headline":"Missing authorization in n/a","id":"CVE-2015-8214","kev_date_added":null,"published":"2015-11-27"},{"cvss_score":7.5,"headline":"Denial of service in SIMATIC CP 343-1","id":"CVE-2023-51440","kev_date_added":null,"published":"2024-02-13"},{"cvss_score":6.5,"headline":"Other in SIMATIC CP 343-1 (incl. SIPLUS variants)","id":"CVE-2018-4843","kev_date_added":null,"published":"2018-03-20"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2016-8672","kev_date_added":null,"published":"2016-11-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-06","vendors":["n/a"]},"summary":"Remote attackers can perform actions with authenticated user permissions via CSRF on the integrated web server of affected SIMATIC devices.","url":"https://insights.sbomify.com/CVE-2016-8673/"}