Skip to content
Fencer Intel
high 7.8

CVE-2018-12179 json

Improper configuration in system firmware for EDK II may allow unauthenticated user to potentially enable escalation of privilege, informat…

published 7y ago modified 4mo ago also EUVD-2018-4157

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

Improper configuration in system firmware for EDK II may allow unauthenticated user to potentially enable escalation of privilege, information disclosure and/or denial of service via local access.

Patch / fix

  • edk2 Debian 14, Debian 13, Debian 12 0~20190606.20d2e5a1-2

debian advisories DEBIAN-CVE-2018-12179

Is CVE-2018-12179 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-12179 updated cvss 7.8

edk2: improper configuration insystem firmware leads to privilege escalation

  • Red Hat Enterprise Linux 7 ovmf, OVMF, AAVMF Red Hat Enterprise Linux 8 edk2, edk2-ovmf, edk2-aarch64 Red Hat Virtualization 4 redhat-virtualization-host-image-update
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Extensible Firmware Interface Development Kit (EDK II) Extensible Firmware Interface Development Kit (EDK II)

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.