CVE-2022-22211: Junos OS Evolved: PTX Series: Multiple FPCs become unreachable due to continuous polling of specific SNMP OID
A limitless resource allocation vulnerability in FPC resources of Juniper Networks Junos OS Evolved on PTX Series allows an unprivileged attacker to cause Denial of Service (DoS). Continuously polling the SNMP jnxCosQstatTable causes the FPC to run out of GUID space, causing a Denial of Service to the FPC resources. When the FPC runs out of the GUID space, you will see the following syslog messages. The evo-aftmand-bt process is asserting. fpc1 evo-aftmand-bt[17556]: %USER-3: getnextguid: Ran out of Guid Space start 1748051689472 end 1752346656767 fpc1 audit[17556]: %AUTH-5: ANOMABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=17556 comm="EvoAftManBt-mai" exe="/usr/sbin/evo-aftmand-bt" sig=6 fpc1 kernel: %KERN-5: audit: type=1701 audit(1648567505.119:57): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=17556 comm="EvoAftManBt-mai" exe="/usr/sbin/evo-aftmand-bt" sig=6 fpc1 emfd-fpa[14438]: %USER-5: Alarm set: APP color=red, class=CHASSIS, reason=Application evo-aftmand-bt fail on node Fpc1 fpc1 emfd-fpa[14438]: %USER-3-EMFFPAALARMREP: RaiseAlarm: Alarm(Location: /Chassis[0]/Fpc[1] Module: sysman Object: evo-aftmand-bt:0 Error: 2) reported fpc1 sysepochman[12738]: %USER-5-SYSTEMREBOOTEVENT: Reboot [node] [ungraceful reboot] [evo-aftmand-bt exited] The FPC resources can be monitored using the following commands: user@router> start shell [vrf:none] user@router-re0:~$ cli -c "show platform application-info allocations app evo-aftmand-bt" | grep ^fpc | grep -v Route | grep -i -v Nexthop | awk '{total[$1] += $5} END { for (key in total) { print key " " total[key]/4294967296 }}' Once the FPCs become unreachable they must be manually restarted as they do not self-recover. This issue affects Juniper Networks Junos OS Evolved on PTX Series: All versions prior to 20.4R3-S4-EVO; 21.1-EVO version 21.1R1-EVO and later versions; 21.2-EVO version 21.2R1-EVO and later versions; 21.3-EVO versions prior to 21.3R3-EVO; 21.4-EVO versions prior to 21.4R2-EVO; 22.1-EVO versions prior to 22.1R2-EVO.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Juniper Networks Junos OS Evolved on PTX Seriesto a version that resolves this vulnerability.Fixed in 20.4R3-S4-EVO - Upgrade
Upgrade
Juniper Networks Junos OS Evolved on PTX Seriesto a version that resolves this vulnerability.Fixed in 21.3R3-EVO - Upgrade
Upgrade
Juniper Networks Junos OS Evolved on PTX Seriesto a version that resolves this vulnerability.Fixed in 21.4R2-EVO - Upgrade
Upgrade
Juniper Networks Junos OS Evolved on PTX Seriesto a version that resolves this vulnerability.Fixed in 22.1R2-EVO - Upgrade
Upgrade
Juniper Networks Junos OS Evolved on PTX Seriesto a version that resolves this vulnerability.Fixed in 22.2R1-EVO - Operational
After upgrading, if any FPC resources become unreachable (including those caused by continuous polling of specific SNMP OIDs), manually restart the affected FPCs because they do not self-recover.
Event History
Frequently Asked Questions
What is CVE-2022-22211 vulnerability?
CVE-2022-22211 is a limitless resource allocation vulnerability in FPC resources of Juniper Networks Junos OS Evolved on PTX Series that allows an unprivileged attacker to cause Denial of Service (DoS) by continuously polling the SNMP jnxCosQstatTable.
How to fix CVE-2022-22211 vulnerability?
To fix CVE-2022-22211 vulnerability, Juniper Networks has released security advisories along with patches and updates. It is recommended to apply the necessary patches as soon as possible.
What is the severity of CVE-2022-22211 vulnerability?
The severity of CVE-2022-22211 vulnerability is rated as high with a CVSS score of 7.5.
Is Juniper Ptx Series affected by CVE-2022-22211 vulnerability?
No, Juniper Ptx Series devices are not vulnerable to the CVE-2022-22211 vulnerability.