CVE Vulnerabilities

CVE-2020-14152

Uncontrolled Resource Consumption

Published: Jun 15, 2020 | Modified: Feb 27, 2023
CVSS 3.x
7.1
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
CVSS 2.x
5.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:P
RedHat/V2
RedHat/V3
7.1 MODERATE
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
Ubuntu
LOW

In IJG JPEG (aka libjpeg) before 9d, jpeg_mem_available() in jmemnobs.c in djpeg does not honor the max_memory_to_use setting, possibly causing excessive memory consumption.

Weakness

The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.

Affected Software

Name Vendor Start Version End Version
Libjpeg Ijg * 9d (excluding)
Libjpeg-turbo Ubuntu esm-infra/xenial *
Libjpeg-turbo Ubuntu precise/esm *
Libjpeg-turbo Ubuntu trusty *
Libjpeg-turbo Ubuntu trusty/esm *
Libjpeg-turbo Ubuntu upstream *
Libjpeg-turbo Ubuntu xenial *
Libjpeg6b Ubuntu bionic *
Libjpeg6b Ubuntu devel *
Libjpeg6b Ubuntu eoan *
Libjpeg6b Ubuntu esm-apps/bionic *
Libjpeg6b Ubuntu esm-apps/focal *
Libjpeg6b Ubuntu esm-apps/jammy *
Libjpeg6b Ubuntu esm-apps/noble *
Libjpeg6b Ubuntu esm-apps/xenial *
Libjpeg6b Ubuntu focal *
Libjpeg6b Ubuntu groovy *
Libjpeg6b Ubuntu hirsute *
Libjpeg6b Ubuntu impish *
Libjpeg6b Ubuntu jammy *
Libjpeg6b Ubuntu kinetic *
Libjpeg6b Ubuntu lunar *
Libjpeg6b Ubuntu mantic *
Libjpeg6b Ubuntu noble *
Libjpeg6b Ubuntu trusty *
Libjpeg6b Ubuntu trusty/esm *
Libjpeg6b Ubuntu upstream *
Libjpeg6b Ubuntu xenial *
Libjpeg9 Ubuntu bionic *
Libjpeg9 Ubuntu eoan *
Libjpeg9 Ubuntu esm-apps/bionic *
Libjpeg9 Ubuntu esm-apps/xenial *
Libjpeg9 Ubuntu trusty *
Libjpeg9 Ubuntu upstream *
Libjpeg9 Ubuntu xenial *

Extended Description

Limited resources include memory, file system storage, database connection pool entries, and CPU. If an attacker can trigger the allocation of these limited resources, but the number or size of the resources is not controlled, then the attacker could cause a denial of service that consumes all available resources. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system. There are at least three distinct scenarios which can commonly lead to resource exhaustion:

Resource exhaustion problems are often result due to an incorrect implementation of the following situations:

Potential Mitigations

  • Mitigation of resource exhaustion attacks requires that the target system either:

  • The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.

  • The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.

References