# CVE-2021-44850: Memory corruption in n/a

> Physical access allows attackers to modify SD boot images, triggering a ROM buffer overflow to bypass secure boot restrictions and execute arbitrary code.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-63r5-j25f-4c6v

## What is CVE-2021-44850?

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.

### Official 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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2021-44850?

It affects 10 products.


Products: Amd Xilinx Z-7007s Firmware, Amd Xilinx Z-7010 Firmware, Amd Xilinx Z-7012s Firmware, Amd Xilinx Z-7014s Firmware, Amd Xilinx Z-7015 Firmware, Amd Xilinx Z-7020 Firmware, Amd Xilinx Z-7030 Firmware, Amd Xilinx Z-7035 Firmware, Amd Xilinx Z-7045 Firmware, Amd Xilinx Z-7100 Firmware.

## How do I fix CVE-2021-44850?

No fix has been published for CVE-2021-44850 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-44850 being exploited?

There is no known exploitation of CVE-2021-44850 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-44850 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2021-44850 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-44850/ (Markdown: https://insights.sbomify.com/CVE-2021-44850/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-44850
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-44850
- OSV: https://osv.dev/vulnerability/CVE-2021-44850

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-44850/
Summaries are generated and may contain mistakes; the official description above is the record.