# CVE-2020-26122: Code injection in n/a

> Administrators can inject malicious code into Inspur server BMC firmware due to missing signature verification, leading to remote code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jvrj-mg4m-mpx3

## What is CVE-2020-26122?

CVE-2020-26122 is a high-severity code injection vulnerability in n/a, published on 7 Dec 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Inspur NF5266M5 through 3.21.2 and other server M5 devices allow remote code execution via administrator privileges. The Baseboard Management Controller (BMC) program of INSPUR server is weak in checking the firmware and lacks the signature verification mechanism, the attacker who obtains the administrator's rights can control the BMC by inserting malicious code into the firmware program and bypassing the current verification mechanism to upgrade the BMC.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 15 products.


Products: Inspur Nf5180m5 Firmware, Inspur Nf5260m5 Firmware, Inspur Nf5266m5 Firmware, Inspur Nf5270m5 Firmware, Inspur Nf5280m5 Firmware, Inspur Nf5466m5 Firmware, Inspur Nf5468m5 Firmware, Inspur Nf5486m5 Firmware, Inspur Nf5488m5-D Firmware, Inspur Nf8260m5 Firmware, Inspur Nf8480m5 Firmware, Inspur Ns5162m5 Firmware, Inspur Ns5482m5 Firmware, Inspur Ns5484m5 Firmware, Inspur Ns5488m5 Firmware.

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

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

## Is CVE-2020-26122 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-26122 is a high-severity code injection vulnerability in n/a, published on 7 Dec 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26122 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-26122/ (Markdown: https://insights.sbomify.com/CVE-2020-26122/index.md)
```

## Sources

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

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