CVE Vulnerabilities

CVE-2020-27814

Heap-based Buffer Overflow

Published: Jan 26, 2021 | Modified: Oct 07, 2022
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
7.8 MODERATE
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

A heap-buffer overflow was found in the way openjpeg2 handled certain PNG format files. An attacker could use this flaw to cause an application crash or in some cases execute arbitrary code with the permission of the user running such an application.

Weakness

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Affected Software

Name Vendor Start Version End Version
Openjpeg Uclouvain * 1.5.1 (including)
Openjpeg Uclouvain 2.0.0 (including) 2.4.0 (excluding)
Blender Ubuntu trusty *
Ghostscript Ubuntu bionic *
Ghostscript Ubuntu trusty *
Ghostscript Ubuntu xenial *
Insighttoolkit4 Ubuntu trusty *
Openjpeg2 Ubuntu bionic *
Openjpeg2 Ubuntu devel *
Openjpeg2 Ubuntu focal *
Openjpeg2 Ubuntu groovy *
Openjpeg2 Ubuntu hirsute *
Openjpeg2 Ubuntu impish *
Openjpeg2 Ubuntu jammy *
Openjpeg2 Ubuntu kinetic *
Openjpeg2 Ubuntu lunar *
Openjpeg2 Ubuntu mantic *
Openjpeg2 Ubuntu noble *
Openjpeg2 Ubuntu oracular *
Openjpeg2 Ubuntu upstream *
Openjpeg2 Ubuntu xenial *
Qtwebengine-opensource-src Ubuntu devel *
Qtwebengine-opensource-src Ubuntu esm-apps/focal *
Qtwebengine-opensource-src Ubuntu esm-apps/jammy *
Qtwebengine-opensource-src Ubuntu esm-apps/noble *
Qtwebengine-opensource-src Ubuntu focal *
Qtwebengine-opensource-src Ubuntu groovy *
Qtwebengine-opensource-src Ubuntu hirsute *
Qtwebengine-opensource-src Ubuntu impish *
Qtwebengine-opensource-src Ubuntu jammy *
Qtwebengine-opensource-src Ubuntu kinetic *
Qtwebengine-opensource-src Ubuntu lunar *
Qtwebengine-opensource-src Ubuntu mantic *
Qtwebengine-opensource-src Ubuntu noble *
Qtwebengine-opensource-src Ubuntu oracular *
Texmaker Ubuntu trusty *
Red Hat Enterprise Linux 8 RedHat openjpeg2-0:2.4.0-4.el8 *

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References