dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2022-22192

HIGH · 7.5 CVSS v3.1 Published 2022-10-18
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 Improper Validation of Syntactic Correctness of Input vulnerability in the kernel of Juniper Networks Junos OS Evolved on PTX series allows a network-based, unauthenticated attacker to cause a Denial of Service (DoS). When an incoming TCP packet destined to the device is malformed there is a possibility of a kernel panic. Only TCP packets destined to the ports for BGP, LDP and MSDP can trigger this. This issue only affects PTX10004, PTX10008, PTX10016. No other PTX Series devices or other platforms are affected. This issue affects Juniper Networks Junos OS Evolved: 20.4-EVO versions prior to 20.4R3-S4-EVO; 21.3-EVO versions prior to 21.3R3-EVO; 21.4-EVO versions prior to 21.4R3-EVO; 22.1-EVO versions prior to 22.1R2-EVO. This issue does not affect Juniper Networks Junos OS Evolved versions prior to 20.4R1-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 vulnerability in the kernel of Juniper Networks Junos OS Evolved on PTX10004, PTX10008, and PTX10016 allows unauthenticated network attackers to cause kernel panic and DoS by sending malformed TCP packets to BGP, LDP, or MSDP ports. The issue stems from improper validation of syntactic correctness of input, leading to a kernel panic when malformed packets are processed.

MitigationUpgrade Junos OS Evolved to the fixed versions (20.4R3-S4-EVO, 21.3R3-EVO, 21.4R3-EVO, or 22.1R2-EVO or later) for affected PTX platforms. Consider filtering or rate-limiting untrusted traffic to BGP/LDP/MSDP ports as a temporary mitigation if immediate upgrade is not feasible.

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= 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. Identify hardware platform
    Run 'show chassis hardware' or check the model number of the device. This vulnerability only affects PTX10004, PTX10008, and PTX10016 routers.
    Affected if The device is a PTX10004, PTX10008, or PTX10016
  2. Check Junos OS Evolved version
    Run 'show version' or 'system ?' command to display the installed Junos OS Evolved version.
    Affected if The version is exactly 20.4, 21.3, 21.4, or 22.1 (any variant within these major.minor releases)
  3. Verify BGP service is enabled
    Run 'show protocols bgp' or 'show configuration protocols bgp' to check if BGP is configured and enabled.
    Affected if BGP is configured and active on the device
  4. Verify LDP service is enabled
    Run 'show protocols ldp' or 'show configuration protocols ldp' to check if LDP is configured and enabled.
    Affected if LDP is configured and active on the device
  5. Verify MSDP service is enabled
    Run 'show protocols msdp' or 'show configuration protocols msdp' to check if MSDP is configured and enabled.
    Affected if MSDP is configured and active on the device
  6. Assess network exposure of BGP/LDP/MSDP ports
    Check firewall filters, routing policy, and interface configurations to determine if BGP (TCP port 179), LDP (UDP/TCP port 646), or MSDP (TCP port 639) ports are accessible from untrusted network segments.
    Affected if Any of BGP, LDP, or MSDP services are exposed to untrusted or external network interfaces

A user is affected if they run Junos OS Evolved version 20.4, 21.3, 21.4, or 22.1 on a PTX10004, PTX10008, or PTX10016 platform with BGP, LDP, or MSDP services enabled and accessible from the network.

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 the fixed versions (20.4R3-S4-EVO, 21.3R3-EVO, 21.4R3-EVO, or 22.1R2-EVO or later) for affected PTX platforms. Consider filtering or rate-limiting untrusted traffic to BGP/LDP/MSDP ports as a temporary mitigation if immediate upgrade is not feasible.

Recommended fix High confidence

20.4R3-S4-EVO (or later for 20.4 branch), 21.3R3-EVO (or later for 21.3 branch), 21.4R3-EVO (or later for 21.4 branch), 22.1R2-EVO (or later for 22.1 branch)

  1. 1. Identify the current Junos OS Evolved version on the affected PTX device (PTX10004, PTX10008, or PTX10016) using 'show version' command
  2. 2. Determine which version branch (20.4-EVO, 21.3-EVO, 21.4-EVO, or 22.1-EVO) the current software matches
  3. 3. Download the appropriate fixed version for your branch from the Juniper Networks support portal
  4. 4. For 20.4-EVO systems: upgrade to 20.4R3-S4-EVO or later
  5. 5. For 21.3-EVO systems: upgrade to 21.3R3-EVO or later
  6. 6. For 21.4-EVO systems: upgrade to 21.4R3-EVO or later
  7. 7. For 22.1-EVO systems: upgrade to 22.1R2-EVO or later
  8. 8. Upload the new image to the device using 'request system software add' command

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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