Skip to content
Fencer Intel
critical 9.8

CVE-2019-11059 json

Das U-Boot 2016.11-rc1 through 2019.04 mishandles the ext4 64-bit extension, resulting in a buffer overflow.

published 7y ago modified 4mo ago also EUVD-2019-2767

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

Summary

Das U-Boot 2016.11-rc1 through 2019.04 mishandles the ext4 64-bit extension, resulting in a buffer overflow.

Patch / fix

  • u-boot Debian 14, Debian 13, Debian 12 2019.01+dfsg-6

debian advisories DEBIAN-CVE-2019-11059

  • u-boot SLES 12 SP3-LTSS, Enterprise Storage 5 2016.07-12.3.1
  • u-boot-rpi3 SLES 12 SP3-LTSS, Enterprise Storage 5 2016.07-12.3.1
  • u-boot SLES for SAP 15, SLES 15-LTSS, SLE High Performance Computing 15-LTSS +1 more 2018.03-4.6.1
  • u-boot-rpi3 SLES 15-LTSS, SLE High Performance Computing 15-LTSS, SLE High Performance Computing 15-ESPOS 2018.03-4.6.2
  • u-boot SLE Module for Basesystem 15 SP1 2019.01-7.10.1
  • u-boot-rpi3 SLE Module for Basesystem 15 SP1 2019.01-7.10.2
  • u-boot SLES for SAP 12 SP5, SLES 12 SP5 2019.01-5.3.1
  • u-boot-rpi3 SLES for SAP 12 SP5, SLES 12 SP5 2019.01-5.3.1

suse advisories SUSE-SU-2020:3474-1SUSE-SU-2020:3283-1SUSE-SU-2020:3282-1SUSE-SU-2020:3256-1SUSE-SU-2020:3255-1

  • u-boot openSUSE Leap 15.1 2019.01-lp151.6.13.1

opensuse advisories openSUSE-SU-2020:1930-1

Is CVE-2019-11059 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

Exploit prediction

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

CVSS scores

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

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.