Summary
It was discovered that libjpeg-turbo was not properly handling EOF characters,
which could lead to excessive memory consumption through the execution of a
large loop. An attacker could possibly use this issue to cause a denial of
service. (CVE-2018-11813)
It was discovered that libjpeg-turbo was not properly performing bounds
check operations, which could lead to a heap-based buffer overread. If a user
or automated system were tricked into opening a specially crafted file, an
attacker could possibly use this issue to cause a denial of service. This
issue only affected Ubuntu 14.04 ESM. (CVE-2018-14498)
It was discovered that libjpeg-turbo was not properly limiting the amount of
main memory being consumed by the system during decompression or multi-pass
compression operations, which could lead to excessive memory consumption. An
attacker could possibly use this issue to cause a denial of service.
(CVE-2020-14152)
It was discovered that libjpeg-turbo was not properly setting variable sizes
when performing certain kinds of encoding operations, which could lead to a
stack-based buffer overflow. If a user or automated system were tricked into
opening a specially crafted file, an attacker could possibly use this issue to
cause a denial of service. (CVE-2020-17541)
Fixed packages 2
| Release | Package | Fixed in |
|---|---|---|
| Ubuntu · Pro 14.04 LTS Pro:14.04:LTS | libjpeg-turbo | 1.3.0-0ubuntu2.1+esm2 |
| Ubuntu · Pro 16.04 LTS Pro:16.04:LTS | libjpeg-turbo | 1.4.2-0ubuntu3.4+esm1 |
Vulnerabilities 4
-
Unscored —
libjpeg 9c has a large loop because read_pixel in rdtarga.c mishandles EOF.
-
Unscored —
get_8bit_row in rdbmp.c in libjpeg-turbo through 1.5.90 and MozJPEG through 3.3.1 allows attackers to cause a denial of…
-
Unscored —
In IJG JPEG (aka libjpeg) before 9d, jpeg_mem_available() in jmemnobs.c in djpeg does not honor the max_memory_to_use s…
-
Unscored —
Libjpeg-turbo all version have a stack-based buffer overflow in the "transform" component. A remote attacker can send a…