{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-7262 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-7262 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-7262 is a medium-severity denial of service vulnerability in n/a, published on 25 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-7262 and fix it if it is affected.\n\nWhat it is: CVE-2017-7262 is a medium-severity denial of service vulnerability in n/a, published on 25 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-7262 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-7262/ (Markdown: https://insights.sbomify.com/CVE-2017-7262/index.md)","id":"CVE-2017-7262","markdown":"https://insights.sbomify.com/CVE-2017-7262/index.md","name":"CVE-2017-7262","record":{"aliases":["GHSA-548h-j794-xmvp"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AMD Ryzen processor","requires_auth":"low_privilege","summary":"Local users can cause a system hang on AMD Ryzen processors by executing a long series of FMA3 instructions, requiring a microcode update.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ryzen","vendor":"amd"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The AMD Ryzen processor with AGESA microcode through 2017-01-27 allows local users to cause a denial of service (system hang) via an application that makes a long series of FMA3 instructions, as demonstrated by the Flops test suite.","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":"Denial of service in n/a","id":"CVE-2017-7262","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2017"},"n_packages":0,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-7263"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2017-7261"},"products":["n/a"],"published":"2017-03-25","related":[],"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":"Local users can cause a system hang on AMD Ryzen processors by executing a long series of FMA3 instructions, requiring a microcode update.","url":"https://insights.sbomify.com/CVE-2017-7262/"}