{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-26407 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-26407 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-26407 is a medium-severity vulnerability in 2nd Gen EPYC, published on 10 Jan 2023. 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-2021-26407 and fix it if it is affected.\n\nWhat it is: CVE-2021-26407 is a medium-severity vulnerability in 2nd Gen EPYC, published on 10 Jan 2023. 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-2021-26407 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-2021-26407/ (Markdown: https://insights.sbomify.com/CVE-2021-26407/index.md)","id":"CVE-2021-26407","markdown":"https://insights.sbomify.com/CVE-2021-26407/index.md","name":"CVE-2021-26407","record":{"aliases":["GHSA-wvcg-5hx9-98xw"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AMD EPYC firmware","requires_auth":"low_privilege","summary":"Weak random IV generation in AMD EPYC firmware may cause collisions, leading to potential information disclosure.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMD","cpe":[{"product":"romepi_firmware","vendor":"amd"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"A randomly generated Initialization Vector (IV) may lead to a collision of IVs with the same key potentially resulting in information disclosure.","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":"Weak cryptography in 2nd Gen EPYC","id":"CVE-2021-26407","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Other in 1st Gen AMD EPYC™","id":"CVE-2021-26408"},"packages":[],"prev":{"headline":"Denial of service in 1st Gen AMD EPYC™ Processors","id":"CVE-2021-26406"},"products":["2nd Gen EPYC"],"published":"2023-01-10","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-08","vendors":[" AMD"]},"summary":"Weak random IV generation in AMD EPYC firmware may cause collisions, leading to potential information disclosure.","url":"https://insights.sbomify.com/CVE-2021-26407/"}