Edk Ii vulnerabilitiesRanked by how likely they are to be used.

Product3 versions
The short answer

Edk Ii is made by Tianocore. We track 11 published vulnerabilities in it, across 3 versions. None of them is on the list of flaws known to be exploited today. If you run Edk Ii, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Edk Ii vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Edk Ii's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Edk Ii flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 2.3%

    Buffer overflow in network stack for EDK II may allow unprivileged user to potentially enable escalation of privilege and/or denial of service via network.

    CVSS9.1Published27 Mar 2019
  2. 2.3%

    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.

    CVSS8.8Published27 Mar 2019
  3. 1.3%

    Buffer overflow in system firmware for EDK II may allow unauthenticated user to potentially enable escalation of privilege and/or denial of service via network access.

    CVSS9.8Published27 Mar 2019
  4. 0.5%

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

    CVSS6.8Published27 Mar 2019
  5. 0.4%

    Logic issue in variable service module for EDK II/UDK2018/UDK2017/UDK2015 may allow an authenticated user to potentially enable escalation of privilege, information disclosure and/or denial of service via local access.

    CVSS7.8Published27 Mar 2019
  6. 0.4%

    Stack overflow in corrupted bmp for EDK II may allow unprivileged user to potentially enable denial of service or elevation of privilege via local access.

    CVSS6.0Published27 Mar 2019
  7. 0.4%

    BootPerformanceTable pointer is read from an NVRAM variable in PEI.

    CVSS7.8Published5 Aug 2021
  8. 0.4%

    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.

    CVSS7.8Published27 Mar 2019
  9. 0.4%

    Insufficient memory write check in SMM service for EDK II may allow an authenticated user to potentially enable escalation of privilege, information disclosure and/or denial of service via local access.

    CVSS6.7Published27 Mar 2019
  10. 0.4%

    Stack overflow in XHCI for EDK II may allow an unauthenticated user to potentially enable denial of service via local access.

    CVSS5.5Published27 Mar 2019
Precursor Intelligence

Running Edk Ii? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 11 published vulnerabilities listed under the name Edk Ii, across 3 versions.

None of Edk Ii's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Edk Ii. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.