{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-9607 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-9607 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-9607 is a high-severity vulnerability in n/a, published on 20 Sep 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-9607 and fix it if it is affected.\n\nWhat it is: CVE-2017-9607 is a high-severity vulnerability in n/a, published on 20 Sep 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-9607 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-2017-9607/ (Markdown: https://insights.sbomify.com/CVE-2017-9607/index.md)","id":"CVE-2017-9607","markdown":"https://insights.sbomify.com/CVE-2017-9607/index.md","name":"CVE-2017-9607","record":{"aliases":["GHSA-vx3j-47rq-fwp6"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ARM Trusted Firmware","requires_auth":"none","summary":"Attackers can exploit an integer overflow in ARM Trusted Firmware to write arbitrary data to secure memory, bypass protections, and cause denial of service.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"trusted_firmware-a","vendor":"trustedfirmware"}],"cvss":{"score":7,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"The BL1 FWU SMC handling code in ARM Trusted Firmware before 1.4 might allow attackers to write arbitrary data to secure memory, bypass the bl1_plat_mem_check protection mechanism, cause a denial of service, or possibly have unspecified other impact via a crafted AArch32 image, which triggers an integer overflow.","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":"Integer overflow in n/a","id":"CVE-2017-9607","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in n/a","id":"CVE-2017-9608"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2017-9606"},"products":["n/a"],"published":"2017-09-20","related":[{"cvss_score":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2017-7563","kev_date_added":null,"published":"2017-06-07"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2017-15031","kev_date_added":null,"published":"2018-12-18"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-7564","kev_date_added":null,"published":"2017-06-07"},{"cvss_score":7.4,"headline":"Information disclosure in n/a","id":"CVE-2022-47630","kev_date_added":null,"published":"2023-01-16"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2018-19440","kev_date_added":null,"published":"2019-01-29"}],"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-05","vendors":["n/a"]},"summary":"Attackers can exploit an integer overflow in ARM Trusted Firmware to write arbitrary data to secure memory, bypass protections, and cause denial of service.","url":"https://insights.sbomify.com/CVE-2017-9607/"}