{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-20522 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-20522 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-20522 is a high-severity denial of service vulnerability in 2nd Gen EPYC, published on 10 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-20522 and fix it if it is affected.\n\nWhat it is: CVE-2023-20522 is a high-severity denial of service vulnerability in 2nd Gen EPYC, published on 10 Jan 2023. 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-2023-20522 in the wild and no public exploit code.\n\nAffected product: 2nd Gen EPYC. 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-2023-20522/ (Markdown: https://insights.sbomify.com/CVE-2023-20522/index.md)","id":"CVE-2023-20522","markdown":"https://insights.sbomify.com/CVE-2023-20522/index.md","name":"CVE-2023-20522","record":{"aliases":["GHSA-4434-6fgr-q9c4"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"AMD EPYC firmware","requires_auth":"none","summary":"An attacker with a malicious BIOS can cause a denial of service on AMD EPYC processors due to insufficient input validation in ASP.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMD","cpe":[{"product":"milanpi_firmware","vendor":"amd"},{"product":"romepi_firmware","vendor":"amd"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Insufficient input validation in ASP may allow an attacker with a malicious BIOS to potentially cause a denial of service.","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 2nd Gen EPYC","id":"CVE-2023-20522","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Race condition in 2nd Gen EPYC","id":"CVE-2023-20523"},"packages":[],"prev":{"headline":"Race condition in 1st Gen AMD EPYC™ Processors","id":"CVE-2023-20521"},"products":["2nd Gen EPYC","3rd Gen EPYC"],"published":"2023-01-10","related":[{"cvss_score":7.8,"headline":"Memory corruption in 3rd Gen EPYC","id":"CVE-2021-26409","kev_date_added":null,"published":"2023-01-10"},{"cvss_score":7.1,"headline":"Memory corruption in 1st Gen EPYC","id":"CVE-2021-46779","kev_date_added":null,"published":"2023-01-10"},{"cvss_score":6.1,"headline":"Other in 2nd Gen EPYC","id":"CVE-2021-46767","kev_date_added":null,"published":"2023-01-10"},{"cvss_score":5.5,"headline":"Denial of service in 2nd Gen EPYC","id":"CVE-2021-46768","kev_date_added":null,"published":"2023-01-10"},{"cvss_score":5.5,"headline":"Memory corruption in 3rd Gen EPYC","id":"CVE-2021-46791","kev_date_added":null,"published":"2023-01-10"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-07","vendors":[" AMD","AMD"]},"summary":"An attacker with a malicious BIOS can cause a denial of service on AMD EPYC processors due to insufficient input validation in ASP.","url":"https://insights.sbomify.com/CVE-2023-20522/"}