dbcve.org
JunosOperating system · Juniper

CVE-2022-22224

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to 19.1 / 20.4 or later.
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 Check or Handling of Exceptional Conditions vulnerability in the processing of a malformed OSPF TLV in Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated adjacent attacker to cause the periodic packet management daemon (PPMD) process to go into an infinite loop, which in turn can cause protocols and functions reliant on PPMD such as OSPF neighbor reachability to be impacted, resulting in a sustained Denial of Service (DoS) condition. The DoS condition persists until the PPMD process is manually restarted. This issue affects: Juniper Networks Junos OS: All versions prior to 19.1R3-S9; 19.2 versions prior to 19.2R3-S5; 19.3 versions prior to 19.3R3-S3; 19.4 versions prior to 19.4R3-S9; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R3-S1; 20.3 versions prior to 20.3R3; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2. Juniper Networks Junos OS Evolved: All versions prior to 20.4R3-S3-EVO; 21.1 versions prior to 21.1R2-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 Junos OS and Junos OS Evolved allows an unauthenticated adjacent attacker to send malformed OSPF TLV packets that cause the periodic packet management daemon (PPMD) to enter an infinite loop. This crashes PPMD, disrupting OSPF neighbor reachability and other PPMD-dependent protocols until the process is manually restarted.

MitigationUpgrade to a patched version of Junos OS or Junos OS Evolved as listed in the vendor advisory. As a temporary workaround, manually restart the PPMD process if exploitation occurs, and limit OSPF adjacency to trusted neighbors via authentication and access controls.

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.1= 19.1= 19.2= 19.3= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1
Junos Os EvolvedOperating system
Affected:< 20.4= 20.4= 21.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
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. Identify the Junos OS version
    Run 'show version' or 'show version detail' on the device CLI to obtain the installed Junos OS version.
    Affected if The version matches one of the affected ranges: Junos versions < 19.1, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1; or Junos OS Evolved versions < 20.4, 20.4, 21.1.
  2. Confirm OSPF protocol is enabled
    Run 'show protocols ospf' to check if OSPF is configured and active on any interface.
    Affected if OSPF is enabled and running on the device.
  3. Check for PPMD process issues
    Run 'show system processes pm' or check system logs (show log messages) for recent PPMD crashes or restarts.
    Affected if PPMD has crashed, is restarting repeatedly, or shows abnormal behavior in logs.
  4. Verify OSPF neighbor status
    Run 'show ospf neighbor' to check the state of OSPF adjacencies.
    Affected if OSPF neighbors are stuck, flapping, or unreachable despite proper network connectivity.
  5. Review system logs for OSPF TLV errors
    Run 'show log messages' and search for OSPF-related errors, TLV parsing failures, or PPMD-related crash entries.
    Affected if Logs contain OSPF TLV parsing errors or PPMD crash indicators.

The device is affected if it runs a vulnerable Junos OS version listed above AND has OSPF protocol enabled, allowing adjacent network attackers to send malformed OSPF TLV packets that crash PPMD.

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 19.1 / 20.4 or later
Fixed in 19.120.4
Interim mitigation

Upgrade to a patched version of Junos OS or Junos OS Evolved as listed in the vendor advisory. As a temporary workaround, manually restart the PPMD process if exploitation occurs, and limit OSPF adjacency to trusted neighbors via authentication and access controls.

Recommended fix High confidence

19.1R3-S9 (or later 19.1R3-Sx), 19.2R3-S5, 19.3R3-S3, 19.4R3-S9, 20.1R3, 20.2R3-S1, 20.3R3, 20.4R3, 21.1R2 for Junos OS; 20.4R3-S3-EVO, 21.1R2-EVO for Junos OS Evolved

  1. Identify the current Junos OS or Junos OS Evolved version installed on the device using 'show version'
  2. For Junos OS: If running 19.1.x, upgrade to 19.1R3-S9 or later; If running 19.2.x, upgrade to 19.2R3-S5 or later; If running 19.3.x, upgrade to 19.3R3-S3 or later; If running 19.4.x, upgrade to 19.4R3-S9 or later; If running 20.1.x, upgrade to 20.1R3 or later; If running 20.2.x, upgrade to 20.2R3-S1 or later; If running 20.3.x, upgrade to 20.3R3 or later; If running 20.4.x, upgrade to 20.4R3 or la
  3. For Junos OS Evolved: If running 20.4.x, upgrade to 20.4R3-S3-EVO or later; If running 21.1.x, upgrade to 21.1R2-EVO or later
  4. Upload the upgrade package to the device and reboot to apply the new version
  5. Verify the upgrade completed successfully using 'show version' and confirm OSPF neighbors are operational
Caveat Review Juniper release notes for known issues and ensure compatibility with existing configurations before upgrading

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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