CVE-2022-22211

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

HIGH
7.5
CVSS Score
Published: October 18, 2022 at 02:46 AM UTC
Updated: June 17, 2026 at 04:28 AM UTC
19 products affected across 2 vendorsJunos OS EvolvedPtx10008Ptx10003

Using Junos OS Evolved by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS Evolved - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 20.4, so it looks safe — our inference, not a vendor statement
juniper-ptx1000 (environment) · juniper-ptx1000-72q (environment) · juniper-ptx10000 (environment) · juniper-ptx10001 (environment) · juniper-ptx10001-36mr (environment) · juniper-ptx100016 (environment) · juniper-ptx10002 (environment) · juniper-ptx10002-60c (environment) · juniper-ptx10003 (environment) · juniper-ptx10003-160c (environment) · juniper-ptx10003-80c (environment) · juniper-ptx10003-81cd (environment) · juniper-ptx10004 (environment) · juniper-ptx10008 (environment) · juniper-ptx10016 (environment) · juniper-ptx3000 (environment) · juniper-ptx5000 (environment)
v < 20.4R3-S4-EVO21.1R1-EVO ≤ v < 21.1-EVO*21.2R1-EVO ≤ v < 21.2-EVO*21.3-EVO ≤ v < 21.3R3-EVO21.4-EVO ≤ v < 21.4R2-EVO22.1-EVO ≤ v < 22.1R2-EVO21.1R1-EVO21.2R1-EVO21.3-EVO21.4-EVO22.1-EVO
Affected range stops below 20.4R3-S4-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.1-EVO*, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2-EVO*, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3R3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R2-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R2-EVO, so it looks safe — our inference, not a vendor statement
All versions
All versions
All versions
All versions
All versions
All versions
All versions
All versions

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHjuniper
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card