# CVE-2018-12180: Memory corruption in Extensible Firmware Interface Development Kit (EDK II)

> A buffer overflow in EDK II BlockIo service allows unauthenticated attackers to escalate privileges, disclose information, or cause denial of service.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-12180, GHSA-9ghw-h32x-5rfx, RHSA-2019:0809, RHSA-2019:0968, RHSA-2019:1116, UBUNTU-CVE-2018-12180

## What is CVE-2018-12180?

CVE-2018-12180 is a high-severity memory corruption vulnerability in Opensuse Leap, published on 27 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in BlockIo service for EDK II may allow an unauthenticated user to potentially enable escalation of privilege, information disclosure and/or denial of service via network access.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redhat-release-virtualization-host` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.3-0.6.el7 |
| `redhat-virtualization-host` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.3-20190418.0.el7_6 |
| `redhat-virtualization-host-image-update` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.3-20190418.0.el7_6 |
| `redhat-virtualization-host-image-update-placeholder` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.3-0.6.el7 |
| `AAVMF` | Red Hat:enterprise_linux:7::server | All versions | 0:20180508-3.gitee3198e672e2.el7_6.1 |
| `OVMF` | Red Hat:enterprise_linux:7::server | All versions | 0:20180508-3.gitee3198e672e2.el7_6.1 |
| `ovmf` | Red Hat:enterprise_linux:7::server | All versions | 0:20180508-3.gitee3198e672e2.el7_6.1 |
| `edk2` | Red Hat:enterprise_linux:8::appstream | All versions | 0:20180508gitee3198e672e2-9.el8_0.1 |
| `edk2-aarch64` | Red Hat:enterprise_linux:8::appstream | All versions | 0:20180508gitee3198e672e2-9.el8_0.1 |
| `edk2-ovmf` | Red Hat:enterprise_linux:8::appstream | All versions | 0:20180508gitee3198e672e2-9.el8_0.1 |

Products: Opensuse Leap, Tianocore Edk Ii.

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

Apply the vendor's patch.

## Is CVE-2018-12180 being exploited?

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

## Other vulnerabilities in Opensuse Leap

- [CVE-2015-4902](https://insights.sbomify.com/CVE-2015-4902/): Oracle Java SE Integrity Check (medium 5.3, exploited in the wild)
- [CVE-2017-14804](https://insights.sbomify.com/CVE-2017-14804/): package builds could use directory traversal to write outside of target area (critical 9.9)
- [CVE-2019-20787](https://insights.sbomify.com/CVE-2019-20787/): Teeworlds before 0.7.4 has an integer overflow when computing a tilemap size. (critical 9.8)
- [CVE-2019-8341](https://insights.sbomify.com/CVE-2019-8341/): Code injection in n/a (critical 9.8)
- [CVE-2019-6438](https://insights.sbomify.com/CVE-2019-6438/): Other in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12180 is a high-severity memory corruption vulnerability in Opensuse Leap, published on 27 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-12180 in the wild and no public exploit code.

Affected product: Opensuse Leap. 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-12180/ (Markdown: https://insights.sbomify.com/CVE-2018-12180/index.md)
```

## Sources

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

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