dbcve.org
JunosOperating system · Juniper

CVE-2023-28970

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-17
Fix available
A fix is available. Upgrade to 21.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 or Handling of Exceptional Conditions vulnerability in packet processing on the network interfaces of Juniper Networks Junos OS on JRR200 route reflector appliances allows an adjacent, network-based attacker sending a specific packet to the device to cause a kernel crash, resulting in a Denial of Service (DoS). Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. This issue can only be triggered by an attacker on the local broadcast domain. Packets routed to the device are unable to trigger this crash. This issue affects Juniper Networks Junos OS on JRR200: All versions prior to 21.2R3-S4; 21.3 versions prior to 21.3R3-S4; 21.4 versions prior to 21.4R3-S3; 22.1 versions prior to 22.1R3-S1; 22.2 versions prior to 22.2R2-S2, 22.2R3; 22.3 versions prior to 22.3R1-S2, 22.3R2; 22.4 versions prior to 22.4R1-S1, 22.4R2.

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 check or handling of exceptional conditions in packet processing on network interfaces of Juniper Networks Junos OS on JRR200 route reflector appliances allows an adjacent attacker on the local broadcast domain to send a specific packet that triggers a kernel crash, causing denial of service. Repeated packets create sustained DoS; routed packets cannot trigger the crash.

MitigationApply the relevant Junos OS software update for the specific version branch (21.2R3-S4, 21.3R3-S4, 21.4R3-S3, 22.1R3-S1, 22.2R2-S2/22.2R3, 22.3R1-S2/22.3R2, or 22.4R1-S1/22.4R2 depending on deployed version).

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:< 21.2= 21.2= 21.3= 21.4= 22.1= 22.2= 22.3= 22.4

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. Confirm JRR200 model
    Identify the device model by running 'show chassis hardware' or checking the physical device label
    Affected if Device is not a JRR200 route reflector appliance, the vulnerability does not apply
  2. Check Junos OS version
    Run 'show version' and note the installed Junos OS version
    Affected if Version matches or falls within: < 21.2, 21.2, 21.3, 21.4, 22.1, 22.2, 22.3, or 22.4 - these are the affected versions
  3. Verify network adjacency exposure
    Review interface configuration using 'show configuration interfaces' and determine if any interfaces are connected to untrusted local broadcast domains
    Affected if Interfaces are accessible to adjacent (local broadcast domain) attackers - this is required for exploitation
  4. Confirm packet processing on affected interfaces
    Check which interfaces are configured and operational using 'show interfaces terse' - the crash is triggered by packets received on the interface, not routed packets
    Affected if Interfaces are up and processing traffic from adjacent sources on the local network

Environment is affected if the device is a JRR200 running a vulnerable Junos version (21.2 through 22.4) and has network interfaces accessible to adjacent attackers on the local broadcast domain.

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 relevant Junos OS software update for the specific version branch (21.2R3-S4, 21.3R3-S4, 21.4R3-S3, 22.1R3-S1, 22.2R2-S2/22.2R3, 22.3R1-S2/22.3R2, or 22.4R1-S1/22.4R2 depending on deployed version).

Recommended fix High confidence

Upgrade to one of: 21.2R3-S4, 21.3R3-S4, 21.4R3-S3, 22.1R3-S1, 22.2R2-S2, 22.2R3, 22.3R1-S2, 22.3R2, 22.4R1-S1, or 22.4R2 depending on your current branch. Prefer the latest stable release in your branch.

  1. 1. Identify the current Junos OS version running on the JRR200 device using 'show version' command
  2. 2. Determine the appropriate upgrade path based on current version branch (21.2, 21.3, 21.4, 22.1, 22.2, 22.3, or 22.4)
  3. 3. Download the appropriate fixed software image from the Juniper Networks support portal (supportportal.juniper.net)
  4. 4. Transfer the software package to the JRR200 device using SCP or USB
  5. 5. Run 'request system software add <package-name>' to install the upgrade
  6. 6. Reboot the device using 'request system reboot' after installation completes
  7. 7. Verify the new version is running with 'show version' after reboot
  8. 8. Confirm the fix is applied by checking 'show version detail' includes the specific Sx patch version
Caveat Standard Junos OS upgrade considerations apply - review release notes for any configuration changes or compatibility notices before upgrading.

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

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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