{"answers":{"affected":"It affects 10 products.","exploited":"There is no known exploitation of CVE-2021-44850 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-44850 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-44850 is a medium-severity memory corruption vulnerability in n/a, published on 10 Feb 2022. 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-44850 and fix it if it is affected.\n\nWhat it is: CVE-2021-44850 is a medium-severity memory corruption vulnerability in n/a, published on 10 Feb 2022. 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-44850 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-2021-44850/ (Markdown: https://insights.sbomify.com/CVE-2021-44850/index.md)","id":"CVE-2021-44850","markdown":"https://insights.sbomify.com/CVE-2021-44850/index.md","name":"CVE-2021-44850","record":{"aliases":["GHSA-63r5-j25f-4c6v"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Zynq-7000 SoC","requires_auth":"none","summary":"Physical access allows attackers to modify SD boot images, triggering a ROM buffer overflow to bypass secure boot restrictions and execute arbitrary code.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"xilinx_z-7007s_firmware","vendor":"amd"},{"product":"xilinx_z-7010_firmware","vendor":"amd"},{"product":"xilinx_z-7012s_firmware","vendor":"amd"},{"product":"xilinx_z-7014s_firmware","vendor":"amd"},{"product":"xilinx_z-7015_firmware","vendor":"amd"},{"product":"xilinx_z-7020_firmware","vendor":"amd"},{"product":"xilinx_z-7030_firmware","vendor":"amd"},{"product":"xilinx_z-7035_firmware","vendor":"amd"},{"product":"xilinx_z-7045_firmware","vendor":"amd"},{"product":"xilinx_z-7100_firmware","vendor":"amd"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"On Xilinx Zynq-7000 SoC devices, physical modification of an SD boot image allows for a buffer overflow attack in the ROM. Because the Zynq-7000's boot image header is unencrypted and unauthenticated before use, an attacker can modify the boot header stored on an SD card so that a secure image appears to be unencrypted, and they will be able to modify the full range of register initialization values. Normally, these registers will be restricted when booting securely. Of importance to this attack are two registers that control the SD card's transfer type and transfer size. These registers could be modified a way that causes a buffer overflow in the ROM.","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":"Memory corruption in n/a","id":"CVE-2021-44850","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2021-44852"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2021-44848"},"products":["n/a"],"published":"2022-02-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Physical access allows attackers to modify SD boot images, triggering a ROM buffer overflow to bypass secure boot restrictions and execute arbitrary code.","url":"https://insights.sbomify.com/CVE-2021-44850/"}