dbcve.org
JunosOperating system · Juniper

CVE-2022-22230

MEDIUM · 6.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 →
70/100
Remediation priority · Elevated
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 Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent unauthenticated attacker to cause DoS (Denial of Service). If another router generates more than one specific valid OSPFv3 LSA then rpd will crash while processing these LSAs. This issue only affects systems configured with OSPFv3, while OSPFv2 is not affected. This issue affects: Juniper Networks Junos OS 19.2 versions prior to 19.2R3-S6; 19.3 version 19.3R2 and later versions; 19.4 versions prior to 19.4R2-S8, 19.4R3-S9; 20.1 version 20.1R1 and later versions; 20.2 versions prior to 20.2R3-S5; 20.3 versions prior to 20.3R3-S5; 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3-S2; 21.2 versions prior to 21.2R3-S1; 21.3 versions prior to 21.3R3-S2; 21.4 versions prior to 21.4R2. Juniper Networks Junos OS Evolved All versions prior to 20.4R3-S5-EVO; 21.1-EVO versions prior to 21.1R3-S2-EVO; 21.2-EVO versions prior to 21.2R3-S1-EVO; 21.3-EVO versions prior to 21.3R3-S2-EVO; 21.4-EVO versions prior to 21.4R2-EVO; 22.1-EVO versions prior to 22.1R2-EVO; 22.2-EVO versions prior to 22.2R2-EVO. This issue does not affect Juniper Networks Junos OS 19.2 versions prior to 19.2R2.

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

Improper input validation in Juniper's Routing Protocol Daemon (rpd) allows an adjacent unauthenticated attacker to crash rpd by sending specific valid OSPFv3 Link State Advertisements (LSAs). The vulnerability only affects systems configured with OSPFv3; OSPFv2 is not impacted.

MitigationApply the appropriate Juniper software update/patch for the affected Junos OS or Junos OS Evolved version. Until patched, consider network segmentation to limit adjacency to trusted routers.

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:= 19.2= 19.3= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1= 21.2= 21.3= 21.4
Junos Os EvolvedOperating system
Affected:= 18.3= 19.1= 19.2= 19.3= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1= 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/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. Check Junos version
    Run 'show version' on the device CLI to obtain the installed Junos OS or Junos OS Evolved version
    Affected if The installed version matches one of the affected versions listed in the CVE (19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, 21.2, 21.3, 21.4 for Junos; 18.3, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, 21.2, 21.3 for Junos OS Evolved)
  2. Verify OSPFv3 is configured
    Run 'show configuration protocols ospf3' or 'show configuration | match ospf3' to check for OSPFv3 protocol configuration
    Affected if OSPFv3 is actively configured on the device; OSPFv2 configuration alone does not expose this vulnerability
  3. Confirm rpd daemon is running
    Run 'show routing daemon' or check process status for rpd to confirm the Routing Protocol Daemon is active
    Affected if rpd is running and OSPFv3 is enabled, making the device vulnerable to the malformed LSA crash
  4. Check OSPFv3 interface bindings
    Run 'show ospf3 interface' to list all interfaces with OSPFv3 enabled
    Affected if Any interface has OSPFv3 active, indicating the attack surface exists

The device is affected only if it runs an affected Junos version AND has OSPFv3 configured and active; devices running only OSPFv2 or unaffected versions are not vulnerable.

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

Apply the appropriate Juniper software update/patch for the affected Junos OS or Junos OS Evolved version. Until patched, consider network segmentation to limit adjacency to trusted routers.

Recommended fix High confidence

Upgrade to the fixed release for your version branch: Junos OS 19.2R3-S6 or later, 19.4R3-S9 or later, 20.4R3-S4 or later, 21.4R2 or later; Junos OS Evolved 20.4R3-S5-EVO or later, 21.4R2-EVO or later

  1. 1. Identify the current Junos OS or Junos OS Evolved version installed using 'show version'
  2. 2. Determine the appropriate upgrade path based on your current version branch
  3. 3. Download the fixed Junos OS release from the Juniper Networks support portal (e.g., 19.2R3-S6, 19.4R3-S9, 20.4R3-S4, 21.4R2 or later)
  4. 4. Schedule a maintenance window as the upgrade requires a system reboot
  5. 5. Back up the current configuration using 'request system configuration rescue save'
  6. 6. Upload the new Junos OS image to the device
  7. 7. Perform the upgrade using 'request system software add <package> reboot'
  8. 8. After reboot, verify the new version with 'show version'
Caveat Standard Junos upgrade risks apply - verify hardware compatibility and review release notes for any configuration changes; test upgrade in lab environment first

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

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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