dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2022-22194

HIGH · 7.5 CVSS v3.1 Published 2022-04-14
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
An Improper Check for Unusual or Exceptional Conditions vulnerability in the packetIO daemon of Juniper Networks Junos OS Evolved on PTX10003, PTX10004, and PTX10008 allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). Continued receipt of these crafted packets will cause a sustained Denial of Service condition. This issue affects Juniper Networks Junos OS Evolved all versions prior to 20.4R2-S3-EVO on PTX10003, PTX10004, and PTX10008. This issue does not affect: Juniper Networks Junos OS Evolved versions 21.1R1-EVO and above; Juniper Networks Junos OS.

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 improper check for unusual or exceptional conditions vulnerability exists in the packetIO daemon of Juniper Networks Junos OS Evolved on PTX10003, PTX10004, and PTX10008 routers. An unauthenticated, network-based attacker can send specially crafted packets to trigger a denial of service in the packetIO daemon, causing sustained DoS conditions.

MitigationUpgrade Junos OS Evolved to version 20.4R2-S3-EVO or later (or 21.1R1-EVO+) on affected PTX platforms. Implement network segmentation or packet filtering to limit exposure to unauthenticated attackers until the upgrade can be applied.

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

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 the router model
    Run 'show chassis hardware' or 'show system information' to confirm the device is a PTX10003, PTX10004, or PTX10008
    Affected if The device is one of these three PTX models and the Junos OS Evolved version is 20.4 or earlier
  2. Check the Junos OS Evolved version
    Run 'show version' or 'show system information' to retrieve the installed Junos OS Evolved version number
    Affected if The installed version is 20.4 or any version below 20.4 (for example, 20.3, 20.2, etc.)
  3. Verify the packetIO daemon is running
    Run 'show system processes' or similar command to list running daemons and confirm packetIO is active
    Affected if The packetIO daemon is running on an affected version of Junos OS Evolved (20.4 or earlier) on a vulnerable PTX platform

A user is affected if they are running Junos OS Evolved version 20.4 or earlier on a PTX10003, PTX10004, or PTX10008 router with the packetIO daemon enabled.

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 Junos OS Evolved to version 20.4R2-S3-EVO or later (or 21.1R1-EVO+) on affected PTX platforms. Implement network segmentation or packet filtering to limit exposure to unauthenticated attackers until the upgrade can be applied.

Recommended fix High confidence

20.4R2-S3-EVO or 21.1R1-EVO and later

  1. 1. Identify the current Junos OS Evolved version on the PTX10003, PTX10004, or PTX10008 device using 'show version' command
  2. 2. Schedule a maintenance window as the upgrade will require a system reboot
  3. 3. Download the fixed Junos OS Evolved software image (20.4R2-S3-EVO or later, or 21.1R1-EVO or later) from the Juniper Networks support portal
  4. 4. Transfer the software image to the device using SCP or USB
  5. 5. Verify the software image integrity using 'request system software validate' command
  6. 6. Install the new software image using 'request system software add <image> reboot' command
  7. 7. After the device reboots, verify the new version is installed using 'show version'
  8. 8. Confirm the packetIO daemon is running normally and the device is fully operational
Caveat Standard Junos OS upgrade considerations apply - ensure configuration compatibility and backup before upgrade; some feature behavior may change between major releases

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22194 — 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-22194 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