dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2022-22211

HIGH · 7.5 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to 20.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A limitless resource allocation vulnerability in the FPC (Flexible PIC Concentrator) resources of Juniper Networks Junos OS Evolved on PTX Series allows an unprivileged attacker to cause Denial of Service by continuously polling the SNMP jnxCosQstatTable. This causes the FPC to exhaust its GUID (Globally Unique Identifier) space, leading to crash of the evo-aftmand-bt process and making the FPC unreachable until manually restarted.

MitigationUpgrade to a patched version (20.4R3-S4-EVO, 21.1R2-EVO, 21.2R2-EVO, 21.3R3-EVO, 21.4R2-EVO, or 22.1R2-EVO or later) or restrict SNMP access to prevent unauthenticated polling of jnxCosQstatTable.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Junos Os EvolvedOperating system
Affected:< 20.4= 20.4= 21.1= 21.2= 21.3= 21.4= 22.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Junos OS Evolved is running
    Run 'show version' or 'show system software' and verify the OS is Junos OS Evolved (not standard Junos OS)
    Affected if The device is running standard Junos OS instead of Junos OS Evolved - this CVE only affects the Evolved variant
  2. Verify PTX Series platform
    Run 'show chassis hardware' or 'show version' to identify the hardware model
    Affected if The device is not a PTX Series platform - the vulnerability affects only PTX Series devices
  3. Check installed Junos OS Evolved version
    Run 'show version' and compare the version number against the affected ranges: < 20.4, 20.4, 21.1, 21.2, 21.3, 21.4, or 22.1
    Affected if The installed version matches one of the affected version numbers listed in the CVE
  4. Determine if SNMP is enabled and accessible
    Run 'show snmp statistics' or check SNMP configuration via 'show configuration snmp'; verify if SNMP community strings or v3 users are configured and accessible from the attacker's network location
    Affected if SNMP is enabled and accessible from untrusted networks - the exploitation requires polling the jnxCosQstatTable via SNMP

The device is affected if it is a PTX Series running Junos OS Evolved version 20.4, 21.1, 21.2, 21.3, 21.4, or 22.1 (or any version below 20.4) with SNMP enabled and accessible to the attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 20.4 or later
Fixed in 20.4
Interim mitigation

Upgrade to a patched version (20.4R3-S4-EVO, 21.1R2-EVO, 21.2R2-EVO, 21.3R3-EVO, 21.4R2-EVO, or 22.1R2-EVO or later) or restrict SNMP access to prevent unauthenticated polling of jnxCosQstatTable.

Recommended fix High confidence

20.4R3-S4-EVO or later (20.4 branch); 21.3R3-EVO or later (21.x branches); 21.4R2-EVO or later (21.4 branch); 22.1R2-EVO or later (22.1 branch)

  1. 1. Identify the current Junos OS Evolved version running on the PTX Series device using 'show version'
  2. 2. Based on your current version, upgrade to the minimum fixed release: For 20.4.x upgrade to 20.4R3-S4-EVO or later; For 21.1.x or 21.2.x upgrade to 21.3R3-EVO or later; For 21.3.x upgrade to 21.3R3-EVO or later; For 21.4.x upgrade to 21.4R2-EVO or later; For 22.1.x upgrade to 22.1R2-EVO or later
  3. 3. Download the appropriate Junos OS Evolved software image from the Juniper Networks download portal (kb.juniper.net)
  4. 4. Upload the software image to the device using 'request system software add <path-to-package>'
  5. 5. Reboot the device to apply the upgrade using 'request system reboot'
  6. 6. After reboot, verify the new version is running with 'show version'
  7. 7. Monitor FPC resources using 'show platform application-info allocations app evo-aftmand-bt' to confirm GUID space is no longer being exhausted
Caveat Major version upgrades may introduce configuration changes; review release notes for backward compatibility considerations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22211 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22211 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data