dbcve.org
JunosOperating system · Juniper

CVE-2022-22169

MEDIUM · 5.9 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to 21.2 or later.
See remediation →
68/100
Remediation priority · Elevated
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 Initialization vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker who sends specific packets in certain orders and at specific timings to force OSPFv3 to unexpectedly enter graceful-restart (GR helper mode) even though there is not any Grace-LSA received in OSPFv3 causing a Denial of Service (DoS). Unexpectedly entering GR helper mode might cause the OSPFv3 neighbor adjacency formed on this interface to be stuck in the "INIT" state which can be observed by issuing the following command: user@device> show ospf3 neighbor ID Interface State xx.xx.xx.xx ae100.0 Init <<<<<<<<<< An indicator of compromise can be seen in log files when traceoptions for OSPFv3 are enabled before the issue occurs. These logfile messages are as follows: OSPF restart signaling: Received hello with LR bit set from nbr ip=xx::xx id=xx.xx.xx.xx. Set oob-resync capabilty 1. OSPF Restart Signaling: Start helper mode for nbr ip xx::xx id xx.xx.xx.xx OSPF restart signaling: abort helper mode for nbr ip=xx::xx id=xx.xx.xx.xx OSPF neighbor xx::xx (realm ipv6-unicast <interface.unit> area xx.xx.xx.xx) state changed from Full to Init due to 1WayRcvd (event reason: neighbor is in one-way mode) (nbr helped: 0) This issue affects: Juniper Networks Junos OS. 15.1 versions prior to 15.1R7-S11; 18.3 versions prior to 18.3R3-S6; 18.4 versions prior to 18.4R2-S9, 18.4R3-S10; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S7, 19.2R3-S4; 19.3 versions prior to 19.3R2-S7, 19.3R3-S4; 19.4 versions prior to 19.4R3-S6; 20.1 versions prior to 20.1R3-S1; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R2-S2, 20.4R3; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R1-S1, 21.2R2. This issue does not affect any version of Juniper Networks Junos OS 12.3. This issue affects Juniper Networks Junos OS Evolved all versions prior to 21.2R2-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

An Improper Initialization vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker to send specific packets in certain orders and at specific timings to force OSPFv3 to unexpectedly enter graceful-restart (GR helper mode) without receiving a Grace-LSA, causing neighbor adjacencies to become stuck in the INIT state and resulting in a Denial of Service.

MitigationApply the appropriate Junos OS software update from Juniper Networks that addresses this vulnerability; for systems where immediate patching is not possible, monitor OSPFv3 neighbor states and logs for indicators of compromise as described in the advisory.

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:= 15.1= 18.3= 18.4= 19.1= 19.2= 19.3= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1
Junos Os EvolvedOperating system
Affected:< 21.2= 21.2

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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 OS version
    Run 'show version' command to display the installed Junos OS version
    Affected if The version matches any of these: 15.1, 18.3, 18.4, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, or 21.1 (for Junos) or is below 21.2 or equals 21.2 (for Junos OS Evolved)
  2. Verify OSPFv3 protocol is enabled
    Run 'show protocols ospf3' to check if OSPFv3 is configured and active on the device
    Affected if OSPFv3 is enabled and running on the device
  3. Inspect OSPFv3 neighbor states
    Run 'show ospf3 neighbor' to display all OSPFv3 neighbor adjacencies and their current states
    Affected if Any neighbor is stuck in the INIT state or shows abnormal adjacency behavior
  4. Check system logs for OSPFv3 events
    Run 'show log messages | match ospf3' or 'show log messages | match graceful-restart' to review OSPFv3-related system messages
    Affected if Logs show unexpected graceful-restart events for OSPFv3 without corresponding Grace-LSA messages or show OSPFv3 neighbor state anomalies

You are affected if your device runs a vulnerable Junos version AND has OSPFv3 enabled, with neighbors stuck in INIT state or suspicious OSPFv3 GR activity in logs.

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 21.2 or later
Fixed in 21.2
Interim mitigation

Apply the appropriate Junos OS software update from Juniper Networks that addresses this vulnerability; for systems where immediate patching is not possible, monitor OSPFv3 neighbor states and logs for indicators of compromise as described in the advisory.

Recommended fix High confidence

Upgrade to the appropriate fixed version: Junos OS 15.1R7-S11 or later, 18.3R3-S6 or later, 18.4R3-S10 or later, 19.1R3-S7 or later, 19.2R3-S4 or later, 19.3R3-S4 or later, 19.4R3-S6 or later, 20.1R3-S1 or later, 20.2R3-S3 or later, 20.3R3-S1 or later, 20.4R3 or later, 21.1R3 or later, 21.2R2 or lat

  1. 1. Identify the current Junos OS or Junos OS Evolved version installed on the device using the command: show version
  2. 2. Determine the appropriate fixed release based on the current version branch (e.g., 15.1R7-S11, 18.3R3-S6, 18.4R3-S10, 19.1R3-S7, etc.)
  3. 3. Download the fixed Junos OS release from the Juniper Networks support portal (https://www.juniper.net/customers/csc/access/)
  4. 4. Upload the Junos upgrade package to the device using FTP or SCP
  5. 5. Install the upgrade using the command: request system software add <package-name>
  6. 6. Reboot the device after installation using: request system reboot
  7. 7. Verify the fix is applied by checking the new version with: show version
  8. 8. Confirm OSPFv3 neighbor states are恢复正常 using: show ospf3 neighbor
Caveat Standard Junos upgrade considerations apply - ensure configuration backup, review release notes for any migration steps, and plan maintenance window as upgrade may cause brief network disruption

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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