high
7.5
CWE
770
Advisory Published
Updated

CVE-2022-22211: Junos OS Evolved: PTX Series: Multiple FPCs become unreachable due to continuous polling of specific SNMP OID

First published: Tue Oct 18 2022(Updated: )

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: get_next_guid: Ran out of Guid Space start 1748051689472 end 1752346656767 fpc1 audit[17556]: %AUTH-5: ANOM_ABEND 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-EMF_FPA_ALARM_REP: RaiseAlarm: Alarm(Location: /Chassis[0]/Fpc[1] Module: sysman Object: evo-aftmand-bt:0 Error: 2) reported fpc1 sysepochman[12738]: %USER-5-SYSTEM_REBOOT_EVENT: 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.

Credit: sirt@juniper.net

Affected SoftwareAffected VersionHow to fix
Juniper Junos Os Evolved<20.4
Juniper Junos Os Evolved=20.4
Juniper Junos Os Evolved=20.4-r1
Juniper Junos Os Evolved=20.4-r1-s1
Juniper Junos Os Evolved=20.4-r1-s2
Juniper Junos Os Evolved=20.4-r2
Juniper Junos Os Evolved=20.4-r2-s1
Juniper Junos Os Evolved=20.4-r2-s2
Juniper Junos Os Evolved=20.4-r2-s3
Juniper Junos Os Evolved=20.4-r3
Juniper Junos Os Evolved=20.4-r3-s1
Juniper Junos Os Evolved=20.4-r3-s2
Juniper Junos Os Evolved=20.4-r3-s3
Juniper Junos Os Evolved=21.1
Juniper Junos Os Evolved=21.1-r1
Juniper Junos Os Evolved=21.1-r1-s1
Juniper Junos Os Evolved=21.1-r2
Juniper Junos Os Evolved=21.1-r3
Juniper Junos Os Evolved=21.1-r3-s1
Juniper Junos Os Evolved=21.2
Juniper Junos Os Evolved=21.2-r1
Juniper Junos Os Evolved=21.2-r1-s1
Juniper Junos Os Evolved=21.2-r1-s2
Juniper Junos Os Evolved=21.2-r2
Juniper Junos Os Evolved=21.2-r2-s1
Juniper Junos Os Evolved=21.2-r2-s2
Juniper Junos Os Evolved=21.2-r3
Juniper Junos Os Evolved=21.3
Juniper Junos Os Evolved=21.3-r1
Juniper Junos Os Evolved=21.3-r1-s1
Juniper Junos Os Evolved=21.3-r2
Juniper Junos Os Evolved=21.3-r2-s1
Juniper Junos Os Evolved=21.3-r2-s2
Juniper Junos Os Evolved=21.4
Juniper Junos Os Evolved=21.4-r1
Juniper Junos Os Evolved=21.4-r1-s1
Juniper Junos Os Evolved=21.4-r1-s2
Juniper Junos Os Evolved=22.1-r1
Juniper Junos Os Evolved=22.1-r1-s1
Juniper Junos Os Evolved=22.1-r1-s2
Juniper Ptx1000
Juniper Ptx1000-72q
Juniper Ptx10000
Juniper Ptx10001
Juniper Ptx10001-36mr
Juniper Ptx100016
Juniper Ptx10002
Juniper Ptx10002-60c
Juniper Ptx10003
Juniper Ptx10003 160c
Juniper Ptx10003 80c
Juniper Ptx10003 81cd
Juniper Ptx10004
Juniper Ptx10008
Juniper Ptx10016
Juniper Ptx3000
Juniper Ptx5000

Remedy

The following software releases have been updated to resolve this specific issue: Junos OS Evolved: 20.4R3-S4-EVO, 21.3R3-EVO, 21.4R2-EVO, 22.1R2-EVO, 22.2R1-EVO, and all subsequent releases.

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

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.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203