An Uncontrolled Resource Consumption vulnerability in the PFE management daemon (evo-pfemand) of Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause an FPC crash leading to a Denial of Service (DoS). When a specific SNMP GET operation or a specific CLI command is executed this will cause a GUID resource leak, eventually leading to exhaustion and result in an FPC crash and reboot. GUID exhaustion will trigger a syslog message like one of the following for example: evo-pfemand[]: get_next_guid: Ran out of Guid Space … evo-aftmand-zx[]: get_next_guid: Ran out of Guid Space … This leak can be monitored by running the following command and taking note of the value in the rightmost column labeled Guids: user@host> show platform application-info allocations app evo-pfemand | match IFDId|IFLId|Context Node Application Context Name Live Allocs Fails Guids re0 evo-pfemand net::juniper::interfaces::IFDId 0 3448 0 3448 re0 evo-pfemand net::juniper::interfaces::IFLId 0 561 0 561 user@host> show platform application-info allocations app evo-pfemand | match IFDId|IFLId|Context Node Application Context Name Live Allocs Fails Guids re0 evo-pfemand net::juniper::interfaces::IFDId 0 3784 0 3784 re0 evo-pfemand net::juniper::interfaces::IFLId 0 647 0 647 This issue affects Juniper Networks Junos OS Evolved: All versions prior to 20.4R3-S3-EVO; 21.1-EVO version 21.1R1-EVO and later versions; 21.2-EVO versions prior to 21.2R3-S4-EVO; 21.3-EVO version 21.3R1-EVO and later versions; 21.4-EVO versions prior to 21.4R2-EVO.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Junos_os_evolved | Juniper | 20.4 (including) | 20.4 (including) |
| Junos_os_evolved | Juniper | 20.4-r1 (including) | 20.4-r1 (including) |
| Junos_os_evolved | Juniper | 20.4-r1-s1 (including) | 20.4-r1-s1 (including) |
| Junos_os_evolved | Juniper | 20.4-r1-s2 (including) | 20.4-r1-s2 (including) |
| Junos_os_evolved | Juniper | 20.4-r2 (including) | 20.4-r2 (including) |
| Junos_os_evolved | Juniper | 20.4-r2-s1 (including) | 20.4-r2-s1 (including) |
| Junos_os_evolved | Juniper | 20.4-r2-s2 (including) | 20.4-r2-s2 (including) |
| Junos_os_evolved | Juniper | 20.4-r2-s3 (including) | 20.4-r2-s3 (including) |
| Junos_os_evolved | Juniper | 20.4-r3 (including) | 20.4-r3 (including) |
| Junos_os_evolved | Juniper | 20.4-r3-s1 (including) | 20.4-r3-s1 (including) |
| Junos_os_evolved | Juniper | 20.4-r3-s2 (including) | 20.4-r3-s2 (including) |
| Junos_os_evolved | Juniper | 21.1-r1 (including) | 21.1-r1 (including) |
| Junos_os_evolved | Juniper | 21.1-r1-s1 (including) | 21.1-r1-s1 (including) |
| Junos_os_evolved | Juniper | 21.1-r2 (including) | 21.1-r2 (including) |
| Junos_os_evolved | Juniper | 21.1-r3 (including) | 21.1-r3 (including) |
| Junos_os_evolved | Juniper | 21.1-r3-s1 (including) | 21.1-r3-s1 (including) |
| Junos_os_evolved | Juniper | 21.2 (including) | 21.2 (including) |
| Junos_os_evolved | Juniper | 21.2-r1 (including) | 21.2-r1 (including) |
| Junos_os_evolved | Juniper | 21.2-r1-s1 (including) | 21.2-r1-s1 (including) |
| Junos_os_evolved | Juniper | 21.2-r1-s2 (including) | 21.2-r1-s2 (including) |
| Junos_os_evolved | Juniper | 21.2-r2 (including) | 21.2-r2 (including) |
| Junos_os_evolved | Juniper | 21.2-r2-s1 (including) | 21.2-r2-s1 (including) |
| Junos_os_evolved | Juniper | 21.2-r2-s2 (including) | 21.2-r2-s2 (including) |
| Junos_os_evolved | Juniper | 21.2-r3 (including) | 21.2-r3 (including) |
| Junos_os_evolved | Juniper | 21.2-r3-s1 (including) | 21.2-r3-s1 (including) |
| Junos_os_evolved | Juniper | 21.2-r3-s2 (including) | 21.2-r3-s2 (including) |
| Junos_os_evolved | Juniper | 21.2-r3-s3 (including) | 21.2-r3-s3 (including) |
| Junos_os_evolved | Juniper | 21.3-r1 (including) | 21.3-r1 (including) |
| Junos_os_evolved | Juniper | 21.3-r1-s1 (including) | 21.3-r1-s1 (including) |
| Junos_os_evolved | Juniper | 21.3-r2 (including) | 21.3-r2 (including) |
| Junos_os_evolved | Juniper | 21.3-r2-s1 (including) | 21.3-r2-s1 (including) |
| Junos_os_evolved | Juniper | 21.3-r2-s2 (including) | 21.3-r2-s2 (including) |
| Junos_os_evolved | Juniper | 21.3-r3 (including) | 21.3-r3 (including) |
| Junos_os_evolved | Juniper | 21.4 (including) | 21.4 (including) |
| Junos_os_evolved | Juniper | 21.4-r1 (including) | 21.4-r1 (including) |
| Junos_os_evolved | Juniper | 21.4-r1-s1 (including) | 21.4-r1-s1 (including) |
| Junos_os_evolved | Juniper | 21.4-r1-s2 (including) | 21.4-r1-s2 (including) |
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.