dbcve.org
JunosOperating system · Juniper

CVE-2022-22238

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to 19.2 / 20.2 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 for Unusual or Exceptional Conditions vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause a Denial of Service (DoS). When an incoming RESV message corresponding to a protected LSP is malformed it causes an incorrect internal state resulting in an rpd core. This issue affects: Juniper Networks Junos OS All versions prior to 19.2R3-S6; 19.3 versions prior to 19.3R3-S6; 19.4 versions prior to 19.4R3-S8; 20.1 versions prior to 20.1R3-S2; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S2; 20.4 versions prior to 20.4R3-S1; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R1-S2, 21.2R3; 21.3 versions prior to 21.3R2. Juniper Networks Junos OS Evolved All versions prior to 20.2R3-S3-EVO; 20.3-EVO version 20.3R1-EVO and later versions; 20.4-EVO versions prior to 20.4R3-S1-EVO; 21.1-EVO version 21.1R1-EVO and later versions; 21.2-EVO version 21.2R1-EVO and later versions; 21.3-EVO versions prior to 21.3R2-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 routing protocol daemon (rpd) allows an adjacent, unauthenticated attacker to cause a denial of service by sending a malformed RESV message for a protected Label Switched Path (LSP). The improper handling creates an incorrect internal state leading to rpd core dump and service disruption.

MitigationApply the vendor-supplied software updates for affected Junos OS and Junos OS Evolved versions. As an interim measure, restrict layer-2 adjacent network access to prevent unauthorized attackers from reaching the routing infrastructure.

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.2= 19.3= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1= 21.2= 21.3
Junos Os EvolvedOperating system
Affected:< 20.2= 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 OS version
    Run 'show version' or 'system version' command to retrieve the installed Junos OS version
    Affected if The version is 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, 21.2, 21.3, or any version lower than 19.2 (for Junos OS) or lower than/equal to 20.2, 20.3, 20.4, 21.1, 21.2, 21.3 (for Junos OS Evolved)
  2. Verify RSVP protocol is enabled
    Run 'show protocols rsvp' to check if RSVP is configured and active on the device
    Affected if RSVP is enabled and running on the device
  3. Confirm protected LSPs exist
    Run 'show mpls lsp' or 'show label-switched-path' to list configured Label Switched Paths and check their protection status (look for 'protect' or 'primary' with protection configured)
    Affected if One or more protected LSPs are configured in the RSVP network
  4. Assess layer-2 network exposure
    Review network topology and access controls to determine if untrusted adjacent attackers can reach the device over layer-2. Check for untrusted interfaces in the same broadcast domain or examine firewall filter configurations applied to RSVP-enabled interfaces.
    Affected if The device with RSVP and protected LSPs is accessible to unauthenticated adjacent attackers on the layer-2 network

The environment is affected if the device runs a vulnerable Junos OS/Evolved version, has RSVP enabled with protected LSPs configured, and is exposed to layer-2 adjacent unauthenticated attackers who can send malicious RSVP RESV messages.

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.2 / 20.2 or later
Fixed in 19.220.2
Interim mitigation

Apply the vendor-supplied software updates for affected Junos OS and Junos OS Evolved versions. As an interim measure, restrict layer-2 adjacent network access to prevent unauthorized attackers from reaching the routing infrastructure.

Recommended fix High confidence

Upgrade to Junos OS 19.2R3-S6, 19.3R3-S6, 19.4R3-S8, or later stable release; or Junos OS Evolved 20.2R3-S3-EVO, 20.4R3-S1-EVO, or later stable release per the Juniper Networks advisory

  1. 1. Identify current Junos OS or Junos OS Evolved version using 'show version' command
  2. 2. Create a full configuration backup using 'request system configuration backup' or manual configuration export
  3. 3. Schedule a maintenance window as upgrade will require a system restart
  4. 4. Download the appropriate fixed Junos OS release from Juniper Networks (19.2R3-S6, 19.3R3-S6, 19.4R3-S8, or later as listed in official advisory)
  5. 5. For Junos OS Evolved, download the fixed release (20.2R3-S3-EVO, 20.4R3-S1-EVO, or later as listed in official advisory)
  6. 6. Upload the new Junos image to the device using 'request system software add' or equivalent
  7. 7. Reboot the device to apply the new Junos version using 'request system reboot'
  8. 8. After reboot, verify the new version is running with 'show version'
Caveat Review Juniper upgrade guidelines for your specific hardware platform; some upgrades may require intermediate releases; RSVP-TE configuration should be tested post-upgrade

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 / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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