dbcve.org
JunosOperating system · Juniper

CVE-2023-22407

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-13
Fix available
A fix is available. Upgrade to 18.4 / 19.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 Incomplete Cleanup vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS). An rpd crash can occur when an MPLS TE tunnel configuration change occurs on a directly connected router. This issue affects: Juniper Networks Junos OS All versions prior to 18.4R2-S7; 19.1 versions prior to 19.1R3-S2; 19.2 versions prior to 19.2R3; 19.3 versions prior to 19.3R3; 19.4 versions prior to 19.4R3; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2. Juniper Networks Junos OS Evolved All versions prior to 19.2R3-EVO; 19.3 versions prior to 19.3R3-EVO; 19.4 versions prior to 19.4R3-EVO; 20.1 versions prior to 20.1R3-EVO; 20.2 versions prior to 20.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 incomplete cleanup vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker to cause rpd to crash when an MPLS TE tunnel configuration change occurs on a directly connected router, resulting in Denial of Service.

MitigationUpgrade to the fixed Junos OS or Junos OS Evolved versions as specified in the Juniper 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:< 18.4= 18.4= 19.1= 19.2= 19.3= 19.4= 20.1= 20.2
Junos Os EvolvedOperating system
Affected:< 19.2= 19.2= 19.3= 19.4= 20.1= 20.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
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 'show version detail' on the device CLI to identify the installed Junos OS version.
    Affected if The displayed version matches one of the affected versions: < 18.4, 18.4, 19.1, 19.2, 19.3, 19.4, 20.1, or 20.2.
  2. Verify MPLS is configured
    Run 'show configuration protocols mpls' to see if MPLS protocol is enabled on the device.
    Affected if MPLS protocol configuration exists on the device.
  3. Check for Traffic Engineering configuration
    Run 'show configuration protocols mpls traffic-engineering' or look for TE-related configuration under the MPLS hierarchy.
    Affected if MPLS Traffic Engineering (TE) tunnels are configured on the device.
  4. Inspect rpd process status
    Run 'show system processes routing' or 'show system processes | match rpd' to check if the routing daemon is running.
    Affected if The rpd process is active and the device meets the version and MPLS TE criteria.

The device is affected if it runs a Junos version in the affected list AND has MPLS Traffic Engineering tunnels configured, making it vulnerable to rpd crash when an adjacent router triggers a TE tunnel configuration change.

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 18.4 / 19.2 or later
Fixed in 18.419.2
Interim mitigation

Upgrade to the fixed Junos OS or Junos OS Evolved versions as specified in the Juniper advisory.

Recommended fix High confidence

Upgrade to 18.4R2-S7 or later for 18.4 branch; 19.1R3-S2 or later for 19.1 branch; 19.2R3 or later for 19.2 branch; 19.3R3 or later for 19.3 branch; 19.4R3 or later for 19.4 branch; 20.1R2 or later for 20.1 branch; 20.2R2 or later for 20.2 branch (or corresponding Junos OS Evolved equivalents)

  1. 1. Identify the currently installed Junos OS or Junos OS Evolved version using 'show version' command
  2. 2. Based on your current version branch, upgrade to the fixed release: For 18.4 branch: upgrade to 18.4R2-S7 or later; For 19.1 branch: upgrade to 19.1R3-S2 or later; For 19.2 branch: upgrade to 19.2R3 or later; For 19.3 branch: upgrade to 19.3R3 or later; For 19.4 branch: upgrade to 19.4R3 or later; For 20.1 branch: upgrade to 20.1R2 or later; For 20.2 branch: upgrade to 20.2R2 or later
  3. 3. For Junos OS Evolved: upgrade to 19.2R3-EVO or later (19.2 branch), 19.3R3-EVO or later (19.3 branch), 19.4R3-EVO or later (19.4 branch), 20.1R3-EVO or later (20.1 branch), or 20.2R2-EVO or later (20.2 branch)
  4. 4. Download the appropriate upgrade package from the Juniper Networks support portal
  5. 5. Upload the upgrade package to the device and initiate the upgrade using 'request system software add <package>'
  6. 6. After upgrade completes, reboot the device using 'request system reboot'
  7. 7. Verify the upgrade was successful and rpd is running using 'show chassis routing-engine' and 'show version'
Caveat Standard Junos upgrade considerations apply - review Juniper upgrade guides for compatibility with hardware platform and ensure configuration compatibility

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-2023-22407 — 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-2023-22407 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