# CVE-2020-14032: Privilege escalation in n/a

> Attackers can escalate privileges and execute code in System Management Mode on ASRock 4x4 BOX-R1000 devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hh7h-prf8-f6h7

## What is CVE-2020-14032?

CVE-2020-14032 is a critical vulnerability in n/a, published on 23 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ASRock 4x4 BOX-R1000 before BIOS P1.40 allows privilege escalation via code execution in the SMM.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2020-14032?

It affects 1 product.


Products: Asrock Box-R1000 Firmware.

## How do I fix CVE-2020-14032?

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

## Is CVE-2020-14032 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14032 and fix it if it is affected.

What it is: CVE-2020-14032 is a critical vulnerability in n/a, published on 23 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14032 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-2020-14032/ (Markdown: https://insights.sbomify.com/CVE-2020-14032/index.md)
```

## Sources

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

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