Stack overflow in XHCI for EDK II may allow an unauthenticated user to potentially enable denial of service via local access.
Vendor
Extensible Firmware Interface Development Kit (EDK II) vulnerabilities
8 published CVES affecting Extensible Firmware Interface Development Kit (EDK II), from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 8
- Critical
- 1
- High
- 3
- Medium
- 4
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
Latest Extensible Firmware Interface Development Kit (EDK II) CVEs
Newest publication first
-
MediumCVSS 5.5 EPSS 0.40%
-
MediumCVSS 6.0 EPSS 0.43%
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.
-
HighCVSS 8.8 EPSS 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.
-
HighCVSS 7.8 EPSS 0.42%
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.
-
CriticalCVSS 9.1 EPSS 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.
-
MediumCVSS 6.7 EPSS 0.41%
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.
-
MediumCVSS 6.8 EPSS 0.50%
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.
-
HighCVSS 7.8 EPSS 0.44%
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.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.