CVE Vulnerabilities

CVE-2022-22161

Uncontrolled Resource Consumption

Published: Jan 19, 2022 | Modified: Feb 11, 2022
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
Ubuntu

An Uncontrolled Resource Consumption vulnerability in the kernel of Juniper Networks Junos OS allows an unauthenticated network based attacker to cause 100% CPU load and the device to become unresponsive by sending a flood of traffic to the out-of-band management ethernet port. Continued receipted of a flood will create a sustained Denial of Service (DoS) condition. Once the flood subsides the system will recover by itself. An indication that the system is affected by this issue would be that an irq handled by the fman process is shown to be using a high percentage of CPU cycles like in the following example output: user@host> show system processes extensive … PID USERNAME PRI NICE SIZE RES STATE TIME WCPU COMMAND 31 root -84 -187 0K 16K WAIT 22.2H 56939.26% irq96: fman0 This issue affects Juniper Networks Junos OS: All versions prior to 18.3R3-S6; 18.4 versions prior to 18.4R2-S9, 18.4R3-S9; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S7, 19.2R3-S3; 19.3 versions prior to 19.3R2-S7, 19.3R3-S4; 19.4 versions prior to 19.4R2-S5, 19.4R3-S5; 20.1 versions prior to 20.1R3-S1; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R2-S2, 20.4R3; 21.1 versions prior to 21.1R2; 21.2 versions prior to 21.2R1-S1, 21.2R2.

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
Junos Juniper * 18.2
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.3 18.3
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 18.4 18.4
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.1 19.1
Junos Juniper 19.2 19.2
Junos Juniper 19.2 19.2
Junos Juniper 19.2 19.2
Junos Juniper 19.2 19.2
Junos Juniper 19.2 19.2
Junos Juniper 19.2 19.2
Junos Juniper 19.2 19.2
Junos Juniper 19.2 19.2
Junos Juniper 19.2 19.2
Junos Juniper 19.2 19.2
Junos Juniper 19.2 19.2
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.3 19.3
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 19.4 19.4
Junos Juniper 20.1 20.1
Junos Juniper 20.1 20.1
Junos Juniper 20.1 20.1
Junos Juniper 20.1 20.1
Junos Juniper 20.1 20.1
Junos Juniper 20.1 20.1
Junos Juniper 20.1 20.1
Junos Juniper 20.1 20.1
Junos Juniper 20.1 20.1
Junos Juniper 20.1 20.1
Junos Juniper 20.2 20.2
Junos Juniper 20.2 20.2
Junos Juniper 20.2 20.2
Junos Juniper 20.2 20.2
Junos Juniper 20.2 20.2
Junos Juniper 20.2 20.2
Junos Juniper 20.2 20.2
Junos Juniper 20.2 20.2
Junos Juniper 20.2 20.2
Junos Juniper 20.2 20.2
Junos Juniper 20.2 20.2
Junos Juniper 20.3 20.3
Junos Juniper 20.3 20.3
Junos Juniper 20.3 20.3
Junos Juniper 20.3 20.3
Junos Juniper 20.3 20.3
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 21.1 21.1
Junos Juniper 21.1 21.1
Junos Juniper 21.1 21.1
Junos Juniper 21.2 21.2
Junos Juniper 21.2 21.2

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