An Uncontrolled Resource Consumption vulnerability in the handling of IPv6 neighbor state change events in Juniper Networks Junos OS allows an adjacent attacker to cause a memory leak in the Flexible PIC Concentrator (FPC) of an ACX5448 router. The continuous flapping of an IPv6 neighbor with specific timing will cause the FPC to run out of resources, leading to a Denial of Service (DoS) condition. Once the condition occurs, further packet processing will be impacted, creating a sustained Denial of Service (DoS) condition, requiring a manual PFE restart to restore service. The following error messages will be seen after the FPC resources have been exhausted: fpc0 DNX_NH::dnx_nh_tag_ipv4_hw_install(),3135: dnx_nh_tag_ipv4_hw_install: BCM L3 Egress create object failed for NH 602 (-14:No resources for operation), BCM NH Params: unit:0 Port:41, L3_INTF:0 Flags: 0x40 fpc0 DNX_NH::dnx_nh_tag_ipv4_hw_install(),3135: dnx_nh_tag_ipv4_hw_install: BCM L3 Egress create object failed for NH 602 (-14:No resources for operation), BCM NH Params: unit:0 Port:41, L3_INTF:0 Flags: 0x40 fpc0 DNX_NH::dnx_nh_tag_ipv4_hw_install(),3135: dnx_nh_tag_ipv4_hw_install: BCM L3 Egress create object failed for NH 602 (-14:No resources for operation), BCM NH Params: unit:0 Port:41, L3_INTF:0 Flags: 0x40 fpc0 DNX_NH::dnx_nh_tag_ipv4_hw_install(),3135: dnx_nh_tag_ipv4_hw_install: BCM L3 Egress create object failed for NH 602 (-14:No resources for operation), BCM NH Params: unit:0 Port:41, L3_INTF:0 Flags: 0x40 This issue only affects the ACX5448 router. No other products or platforms are affected by this vulnerability. This issue affects Juniper Networks Junos OS on ACX5448: 18.4 versions prior to 18.4R3-S10; 19.1 versions prior to 19.1R3-S5; 19.2 versions prior to 19.2R1-S8, 19.2R3-S2; 19.3 versions prior to 19.3R2-S6, 19.3R3-S2; 19.4 versions prior to 19.4R1-S3, 19.4R2-S2, 19.4R3; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R1-S1, 20.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.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Junos | Juniper | 18.4 (including) | 18.4 (including) |
Junos | Juniper | 18.4-r1 (including) | 18.4-r1 (including) |
Junos | Juniper | 18.4-r1-s1 (including) | 18.4-r1-s1 (including) |
Junos | Juniper | 18.4-r1-s2 (including) | 18.4-r1-s2 (including) |
Junos | Juniper | 18.4-r1-s3 (including) | 18.4-r1-s3 (including) |
Junos | Juniper | 18.4-r1-s4 (including) | 18.4-r1-s4 (including) |
Junos | Juniper | 18.4-r1-s5 (including) | 18.4-r1-s5 (including) |
Junos | Juniper | 18.4-r1-s6 (including) | 18.4-r1-s6 (including) |
Junos | Juniper | 18.4-r1-s7 (including) | 18.4-r1-s7 (including) |
Junos | Juniper | 18.4-r2 (including) | 18.4-r2 (including) |
Junos | Juniper | 18.4-r2-s1 (including) | 18.4-r2-s1 (including) |
Junos | Juniper | 18.4-r2-s2 (including) | 18.4-r2-s2 (including) |
Junos | Juniper | 18.4-r2-s3 (including) | 18.4-r2-s3 (including) |
Junos | Juniper | 18.4-r2-s4 (including) | 18.4-r2-s4 (including) |
Junos | Juniper | 18.4-r2-s5 (including) | 18.4-r2-s5 (including) |
Junos | Juniper | 18.4-r2-s6 (including) | 18.4-r2-s6 (including) |
Junos | Juniper | 18.4-r2-s7 (including) | 18.4-r2-s7 (including) |
Junos | Juniper | 18.4-r2-s8 (including) | 18.4-r2-s8 (including) |
Junos | Juniper | 18.4-r3 (including) | 18.4-r3 (including) |
Junos | Juniper | 18.4-r3-s1 (including) | 18.4-r3-s1 (including) |
Junos | Juniper | 18.4-r3-s2 (including) | 18.4-r3-s2 (including) |
Junos | Juniper | 18.4-r3-s3 (including) | 18.4-r3-s3 (including) |
Junos | Juniper | 18.4-r3-s4 (including) | 18.4-r3-s4 (including) |
Junos | Juniper | 18.4-r3-s5 (including) | 18.4-r3-s5 (including) |
Junos | Juniper | 18.4-r3-s6 (including) | 18.4-r3-s6 (including) |
Junos | Juniper | 18.4-r3-s7 (including) | 18.4-r3-s7 (including) |
Junos | Juniper | 18.4-r3-s8 (including) | 18.4-r3-s8 (including) |
Junos | Juniper | 18.4-r3-s9 (including) | 18.4-r3-s9 (including) |
Junos | Juniper | 19.1 (including) | 19.1 (including) |
Junos | Juniper | 19.1-r1 (including) | 19.1-r1 (including) |
Junos | Juniper | 19.1-r1-s1 (including) | 19.1-r1-s1 (including) |
Junos | Juniper | 19.1-r1-s2 (including) | 19.1-r1-s2 (including) |
Junos | Juniper | 19.1-r1-s3 (including) | 19.1-r1-s3 (including) |
Junos | Juniper | 19.1-r1-s4 (including) | 19.1-r1-s4 (including) |
Junos | Juniper | 19.1-r1-s5 (including) | 19.1-r1-s5 (including) |
Junos | Juniper | 19.1-r1-s6 (including) | 19.1-r1-s6 (including) |
Junos | Juniper | 19.1-r2 (including) | 19.1-r2 (including) |
Junos | Juniper | 19.1-r2-s1 (including) | 19.1-r2-s1 (including) |
Junos | Juniper | 19.1-r2-s2 (including) | 19.1-r2-s2 (including) |
Junos | Juniper | 19.1-r2-s3 (including) | 19.1-r2-s3 (including) |
Junos | Juniper | 19.1-r3 (including) | 19.1-r3 (including) |
Junos | Juniper | 19.1-r3-s1 (including) | 19.1-r3-s1 (including) |
Junos | Juniper | 19.1-r3-s2 (including) | 19.1-r3-s2 (including) |
Junos | Juniper | 19.1-r3-s3 (including) | 19.1-r3-s3 (including) |
Junos | Juniper | 19.1-r3-s4 (including) | 19.1-r3-s4 (including) |
Junos | Juniper | 19.2 (including) | 19.2 (including) |
Junos | Juniper | 19.2-r1 (including) | 19.2-r1 (including) |
Junos | Juniper | 19.2-r1-s1 (including) | 19.2-r1-s1 (including) |
Junos | Juniper | 19.2-r1-s2 (including) | 19.2-r1-s2 (including) |
Junos | Juniper | 19.2-r1-s3 (including) | 19.2-r1-s3 (including) |
Junos | Juniper | 19.2-r1-s4 (including) | 19.2-r1-s4 (including) |
Junos | Juniper | 19.2-r1-s5 (including) | 19.2-r1-s5 (including) |
Junos | Juniper | 19.2-r1-s6 (including) | 19.2-r1-s6 (including) |
Junos | Juniper | 19.2-r1-s7 (including) | 19.2-r1-s7 (including) |
Junos | Juniper | 19.2-r2 (including) | 19.2-r2 (including) |
Junos | Juniper | 19.2-r2-s1 (including) | 19.2-r2-s1 (including) |
Junos | Juniper | 19.2-r3 (including) | 19.2-r3 (including) |
Junos | Juniper | 19.2-r3-s1 (including) | 19.2-r3-s1 (including) |
Junos | Juniper | 19.3 (including) | 19.3 (including) |
Junos | Juniper | 19.3-r1 (including) | 19.3-r1 (including) |
Junos | Juniper | 19.3-r1-s1 (including) | 19.3-r1-s1 (including) |
Junos | Juniper | 19.3-r2 (including) | 19.3-r2 (including) |
Junos | Juniper | 19.3-r2-s1 (including) | 19.3-r2-s1 (including) |
Junos | Juniper | 19.3-r2-s2 (including) | 19.3-r2-s2 (including) |
Junos | Juniper | 19.3-r2-s3 (including) | 19.3-r2-s3 (including) |
Junos | Juniper | 19.3-r2-s4 (including) | 19.3-r2-s4 (including) |
Junos | Juniper | 19.3-r2-s5 (including) | 19.3-r2-s5 (including) |
Junos | Juniper | 19.3-r3 (including) | 19.3-r3 (including) |
Junos | Juniper | 19.3-r3-s1 (including) | 19.3-r3-s1 (including) |
Junos | Juniper | 19.4-r1 (including) | 19.4-r1 (including) |
Junos | Juniper | 19.4-r1-s1 (including) | 19.4-r1-s1 (including) |
Junos | Juniper | 19.4-r1-s2 (including) | 19.4-r1-s2 (including) |
Junos | Juniper | 19.4-r2 (including) | 19.4-r2 (including) |
Junos | Juniper | 19.4-r2-s1 (including) | 19.4-r2-s1 (including) |
Junos | Juniper | 20.1-r1 (including) | 20.1-r1 (including) |
Junos | Juniper | 20.1-r1-s1 (including) | 20.1-r1-s1 (including) |
Junos | Juniper | 20.1-r1-s2 (including) | 20.1-r1-s2 (including) |
Junos | Juniper | 20.1-r1-s3 (including) | 20.1-r1-s3 (including) |
Junos | Juniper | 20.1-r1-s4 (including) | 20.1-r1-s4 (including) |
Junos | Juniper | 20.2-r1 (including) | 20.2-r1 (including) |
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:
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.