dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2022-22212

HIGH · 7.5 CVSS v3.1 Published 2022-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An Allocation of Resources Without Limits or Throttling vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS Evolved allows unauthenticated network based attacker to cause a Denial of Service (DoS). On all Junos Evolved platforms hostbound protocols will be impacted by a high rate of specific hostbound traffic from ports on a PFE. Continued receipt of this amount of traffic will create a sustained Denial of Service (DoS) condition. This issue affects Juniper Networks Junos OS Evolved: 21.2 versions prior to 21.2R3-EVO; 21.3 versions prior to 21.3R2-EVO. This issue does not affect Juniper Networks Junos OS Evolved versions prior to 21.2R1.

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 resource exhaustion vulnerability in the Packet Forwarding Engine (PFE) of Junos OS Evolved allows unauthenticated attackers to send high rates of specific hostbound traffic to PFE ports, causing the system to allocate excessive resources and resulting in a sustained Denial of Service condition affecting all hostbound protocols.

MitigationUpgrade Junos OS Evolved to version 21.2R3-EVO or 21.3R2-EVO or later. As an interim measure, implement network-level filtering or rate limiting for hostbound traffic at network edges to reduce the attack surface.

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:= 21.2= 21.3

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. Identify Junos OS Evolved version
    Execute 'show version' or 'show system information' on the device to retrieve the installed Junos OS Evolved version
    Affected if The installed version is exactly 21.2 or 21.3 (or a variant without R suffix indicating base release)
  2. Confirm PFE hostbound traffic processing
    Use 'show interfaces pfe-*' or 'show pfeb stats' commands to observe if the device is processing hostbound traffic to PFE ports
    Affected if The device actively processes hostbound traffic on PFE interfaces, which is the default operational state for most Junos OS Evolved devices acting as routers or switches
  3. Check for abnormal PFE resource allocation
    Monitor 'show system resources' or 'show pfe statistics' for unusually high memory or CPU allocation patterns on the Packet Forwarding Engine
    Affected if PFE resource utilization is abnormally high or steadily increasing without corresponding legitimate traffic increases

A Junos OS Evolved device on version 21.2 or 21.3 that processes hostbound traffic and shows signs of resource exhaustion on the PFE may be affected by this vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS Evolved to version 21.2R3-EVO or 21.3R2-EVO or later. As an interim measure, implement network-level filtering or rate limiting for hostbound traffic at network edges to reduce the attack surface.

Recommended fix High confidence

Upgrade to Junos OS Evolved 21.2R3-EVO or 21.3R2-EVO (or later stable release)

  1. 1. Identify the current Junos OS Evolved version running on the device using 'show version'
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Download the fixed Junos OS Evolved image (21.2R3-EVO or later, or 21.3R2-EVO or later) from the Juniper Networks support portal
  4. 4. Upload the new image to the device using 'request system software add <image>' or similar method
  5. 5. Reboot the device using 'request system reboot' to apply the new software version
  6. 6. After reboot, verify the new version is installed using 'show version'
  7. 7. Confirm the vulnerability is resolved by ensuring the device can handle high-rate hostbound traffic without DoS condition
Caveat Standard Junos OS upgrade precautions apply - ensure configuration backup and plan for potential brief downtime during reboot

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 help mitigating

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-22212 — 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-22212 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