8.8
CVSSv3

CVE-2020-17541

Published: 01/06/2021 Updated: 07/11/2022
CVSS v2 Base Score: 6.8 | Impact Score: 6.4 | Exploitability Score: 8.6
CVSS v3 Base Score: 8.8 | Impact Score: 5.9 | Exploitability Score: 2.8
VMScore: 605
Vector: AV:N/AC:M/Au:N/C:P/I:P/A:P

Vulnerability Summary

It exists 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)

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

libjpeg-turbo libjpeg-turbo

Vendor Advisories

Synopsis Important: OpenShift Virtualization 4110 Images security and bug fix update Type/Severity Security Advisory: Important Topic Red Hat OpenShift Virtualization release 4110 is now available with updates to packages and images that fix several bugs and add enhancementsRed Hat Product Security has rated this update as having a secur ...
Synopsis Important: OpenShift Container Platform 4110 bug fix and security update Type/Severity Security Advisory: Important Topic Red Hat OpenShift Container Platform release 4110 is now available withupdates to packages and images that fix several bugs and add enhancementsThis release includes a security update for Red Hat OpenShift Co ...
Several security issues were fixed in libjpeg-turbo ...
Several security issues were fixed in libjpeg-turbo ...
Libjpeg-turbo all version have a stack-based buffer overflow in the "transform" component A remote attacker can send a malformed jpeg file to the service and cause arbitrary code execution or denial of service of the target service ...
libjpeg-turbo before version 204 has a stack-based buffer overflow in the "transform" component A remote attacker can send a malformed jpeg file to the service and cause arbitrary code execution or denial of service of the target service Note: according to upstream: "Given that the buffer overrun was fully contained within the stack and did no ...