CVE Vulnerabilities


Uncontrolled Resource Consumption

Published: Jul 11, 2019 | Modified: Feb 25, 2021
CVSS 3.x
CVSS 2.x

A vulnerability in the pfe-chassisd Chassis Manager (CMLC) daemon of Juniper Networks Junos OS allows an attacker to cause a Denial of Service (DoS) to the EX4300 when specific valid broadcast packets create a broadcast storm condition when received on the me0 interface of the EX4300 Series device. A reboot of the device is required to restore service. Continued receipt of these valid broadcast packets will create a sustained Denial of Service (DoS) against the device. Affected releases are Juniper Networks Junos OS: 16.1 versions above and including 16.1R1 prior to 16.1R7-S5; 17.1 versions prior to 17.1R3; 17.2 versions prior to 17.2R3; 17.3 versions prior to 17.3R3-S2; 17.4 versions prior to 17.4R2; 18.1 versions prior to 18.1R3; 18.2 versions prior to 18.2R2.


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 16.1 (including) 16.1 (including)
Junos Juniper 16.1-r1 (including) 16.1-r1 (including)
Junos Juniper 16.1-r2 (including) 16.1-r2 (including)
Junos Juniper 16.1-r3 (including) 16.1-r3 (including)
Junos Juniper 16.1-r3-s10 (including) 16.1-r3-s10 (including)
Junos Juniper 16.1-r3-s11 (including) 16.1-r3-s11 (including)
Junos Juniper 16.1-r4 (including) 16.1-r4 (including)
Junos Juniper 16.1-r5 (including) 16.1-r5 (including)
Junos Juniper 16.1-r6 (including) 16.1-r6 (including)
Junos Juniper 16.1-r6-s6 (including) 16.1-r6-s6 (including)

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.