Advisory

USN-4432-1

Also known as: CVE-2020-10713, CVE-2020-14308, CVE-2020-14309, CVE-2020-14310, CVE-2020-14311, CVE-2020-15705, CVE-2020-15706, CVE-2020-15707

Summary

grub2, grub2-signed vulnerabilities

Details

Jesse Michael and Mickey Shkatov discovered that the configuration parser
in GRUB2 did not properly exit when errors were discovered, resulting in
heap-based buffer overflows. A local attacker could use this to execute
arbitrary code and bypass UEFI Secure Boot restrictions. (CVE-2020-10713)

Chris Coulson discovered that the GRUB2 function handling code did not
properly handle a function being redefined, leading to a use-after-free
vulnerability. A local attacker could use this to execute arbitrary code
and bypass UEFI Secure Boot restrictions. (CVE-2020-15706)

Chris Coulson discovered that multiple integer overflows existed in GRUB2
when handling certain filesystems or font files, leading to heap-based
buffer overflows. A local attacker could use these to execute arbitrary
code and bypass UEFI Secure Boot restrictions. (CVE-2020-14309,
CVE-2020-14310, CVE-2020-14311)

It was discovered that the memory allocator for GRUB2 did not validate
allocation size, resulting in multiple integer overflows and heap-based
buffer overflows when handling certain filesystems, PNG images or disk
metadata. A local attacker could use this to execute arbitrary code and
bypass UEFI Secure Boot restrictions. (CVE-2020-14308)

Mathieu Trudel-Lapierre discovered that in certain situations, GRUB2
failed to validate kernel signatures. A local attacker could use this
to bypass Secure Boot restrictions. (CVE-2020-15705)

Colin Watson and Chris Coulson discovered that an integer overflow
existed in GRUB2 when handling the initrd command, leading to a heap-based
buffer overflow. A local attacker could use this to execute arbitrary code
and bypass UEFI Secure Boot restrictions. (CVE-2020-15707)

Severity

Not rated by the source.

Dates

Published
2020-07-29 18:50 UTC
Modified
2026-06-29 13:48 UTC

Affected packages and fixes

grub2

Debian packages (deb) · Ubuntu 16.04

Affected

  • introduced 0, fixed 2.02~beta2-36ubuntu3.26 (ecosystem)

Fixed versions

2.02~beta2-36ubuntu3.26

Fix

  • Fixed version 2.02~beta2-36ubuntu3.26
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

grub2-signed

Debian packages (deb) · Ubuntu 16.04

Affected

  • introduced 0, fixed 1.66.26 (ecosystem)

Fixed versions

1.66.26

Fix

  • Fixed version 1.66.26
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

grub2

Debian packages (deb) · Ubuntu 18.04

Affected

  • introduced 0, fixed 2.02-2ubuntu8.16 (ecosystem)

Fixed versions

2.02-2ubuntu8.16

Fix

  • Fixed version 2.02-2ubuntu8.16
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

grub2-signed

Debian packages (deb) · Ubuntu 18.04

Affected

  • introduced 0, fixed 1.93.18 (ecosystem)

Fixed versions

1.93.18

Fix

  • Fixed version 1.93.18
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

grub2

Debian packages (deb) · Ubuntu 20.04

Affected

  • introduced 0, fixed 2.04-1ubuntu26.1 (ecosystem)

Fixed versions

2.04-1ubuntu26.1

Fix

  • Fixed version 2.04-1ubuntu26.1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

grub2-signed

Debian packages (deb) · Ubuntu 20.04

Affected

  • introduced 0, fixed 1.142.3 (ecosystem)

Fixed versions

1.142.3

Fix

  • Fixed version 1.142.3
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Ubuntu Security Notices · CC BY-SA 4.0

Sources & licences