dbcve.org
JunosOperating system · Juniper

CVE-2022-22228

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 Specified Type of Input vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS allows an attacker to cause an RPD memory leak leading to a Denial of Service (DoS). This memory leak only occurs when the attacker's packets are destined to any configured IPv6 address on the device. This issue affects: Juniper Networks Junos OS 21.1 versions prior to 21.1R3-S2; 21.2 versions prior to 21.2R3-S1; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R2; 22.1 versions prior to 22.1R2. This issue does not affect Juniper Networks Junos OS versions prior to 21.1R1.

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 type of input validation flaw in the Junos OS routing protocol daemon (rpd) allows crafted IPv6 packets to trigger a memory leak. When packets are sent to any configured IPv6 address on the device, the attacker can exhaust RPD memory resources, causing the routing daemon to fail and resulting in a Denial of Service.

MitigationUpgrade Junos OS to one of the fixed versions (21.1R3-S2, 21.2R3-S1, 21.3R3, 21.4R2, or 22.1R2). Until upgrade is possible, consider IPv6 access controls or filtering to block untrusted IPv6 traffic destined to the device.

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
JunosOperating system
Affected:= 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. Identify device OS and version
    Run 'show version' or 'show version detail' to display the Junos OS version installed on the device
    Affected if The displayed version matches 21.1, 21.2, 21.3, 21.4, or 22.1 exactly (these are the affected versions)
  2. Verify IPv6 configuration exists
    Run 'show configuration | match inet6' or 'show ipv6 interface' to list all interfaces with IPv6 addresses configured
    Affected if Any IPv6 address is assigned to an interface on the device, creating the attack surface for this vulnerability
  3. Confirm rpd daemon is active
    Run 'show system processes routing' or check that the routing daemon is operational via 'show system processes | match rpd'
    Affected if The rpd process is running, as this is the component vulnerable to the memory leak when malformed IPv6 packets arrive
  4. Check for IPv6 access controls
    Run 'show configuration firewall' or 'show configuration protocols' to inspect filter rules applied to IPv6 traffic
    Affected if No IPv6 input filtering or firewall filters are applied to block untrusted IPv6 packets, meaning the device is exposed to incoming IPv6 traffic

The device is affected if it runs Junos OS exactly version 21.1, 21.2, 21.3, 21.4, or 22.1 AND has IPv6 configured on any interface, exposing the rpd daemon to crafted packets.

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 to one of the fixed versions (21.1R3-S2, 21.2R3-S1, 21.3R3, 21.4R2, or 22.1R2). Until upgrade is possible, consider IPv6 access controls or filtering to block untrusted IPv6 traffic destined to the device.

Recommended fix High confidence

Upgrade to 21.1R3-S2 / 21.2R3-S1 / 21.3R3 / 21.4R2 / 22.1R2 or later (minimum fixed versions for respective branches)

  1. 1. Back up the current Junos OS configuration using 'request system configuration backup' or 'save <filename>' command
  2. 2. Download the appropriate fixed Junos OS software version from the Juniper Networks support portal (kb.juniper.net)
  3. 3. Transfer the software package to the device using FTP, SCP, or USB storage
  4. 4. Install the software update using 'request system software add <package-name>' command
  5. 5. Reboot the device using 'request system reboot' command to apply the new software
  6. 6. After reboot, verify the fix by checking the Junos version with 'show version' and confirm rpd is stable with 'show system processes extensive | match rpd'
Caveat Standard Junos upgrade considerations apply - review release notes for any configuration changes, and test in a lab environment before production deployment

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

Fix this in Junos 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-22228 — 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-22228 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