# CVE-2018-13787: Misconfiguration in n/a

> Misconfigured firmware descriptor regions allow local OS programs to modify Supermicro server firmware, enabling privilege escalation and code execution.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x8pf-7q32-5293

## What is CVE-2018-13787?

CVE-2018-13787 is a medium-severity vulnerability in n/a, published on 9 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain Supermicro X11S, X10, X9, X8SI, K1SP, C9X299, C7, B1, A2, and A1 products have a misconfigured Descriptor Region, allowing OS programs to modify firmware.

## Which versions are affected by CVE-2018-13787?

It affects 110 products.


Products: Supermicro A1sa Firmware, Supermicro A1sai1 Firmware, Supermicro A1sai Firmware, Supermicro A1sam Firmware, Supermicro A1srm Firmware, Supermicro A2san Firmware, Supermicro A2sap Firmware, Supermicro A2sav Firmware, Supermicro B10drg Firmware, Supermicro B10dri Firmware, Supermicro B10drt Firmware, Supermicro B1dri Firmware, Supermicro B1sa4 Firmware, Supermicro B1sd2tf Firmware, Supermicro C7b250 Firmware, Supermicro C7h270 Firmware, Supermicro C7q270 Firmware, Supermicro C7x99oc Firmware, Supermicro C7z170 Firmware, Supermicro C7z170o Firmware and 90 more.

## How do I fix CVE-2018-13787?

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

## Is CVE-2018-13787 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-13787 and fix it if it is affected.

What it is: CVE-2018-13787 is a medium-severity vulnerability in n/a, published on 9 Jul 2018. 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-2018-13787 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-2018-13787/ (Markdown: https://insights.sbomify.com/CVE-2018-13787/index.md)
```

## Sources

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

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