dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2023-28967

HIGH · 7.5 CVSS v3.1 Published 2023-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
A Use of Uninitialized Resource vulnerability in the Border Gateway Protocol (BGP) software of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated network-based attacker to send specific genuine BGP packets to a device configured with BGP to cause a Denial of Service (DoS) by crashing the Routing Protocol Daemon (rpd). This issue is triggered when the packets attempt to initiate a BGP connection before a BGP session is successfully established. Continued receipt of these specific BGP packets will cause a sustained Denial of Service condition. This issue is triggerable in both iBGP and eBGP deployments. This issue affects: Juniper Networks Junos OS 21.1 version 21.1R1 and later versions prior to 21.1R3-S5; 21.2 version 21.2R1 and later versions prior to 21.2R3-S2; 21.3 version 21.3R1 and later versions prior to 21.3R3-S2; 21.4 versions prior to 21.4R3; 22.1 versions prior to 22.1R3; 22.2 versions prior to 22.2R2. This issue does not affect Juniper Networks Junos OS versions prior to 21.1R1. This issue affects: Juniper Networks Junos OS Evolved 21.1-EVO version 21.1R1-EVO and later versions prior to 21.4R3-EVO; 22.1-EVO versions prior to 22.1R3-EVO; 22.2-EVO versions prior to 22.2R2-EVO. This issue does not affect Juniper Networks Junos OS Evolved versions prior to 21.1R1-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 Use of Uninitialized Resource vulnerability in Juniper Networks Junos OS and Junos OS Evolved BGP software allows an unauthenticated network-based attacker to send specific BGP packets before session establishment to crash the Routing Protocol Daemon (rpd), causing Denial of Service. The vulnerability affects both iBGP and eBGP deployments and can be sustained through continued receipt of malicious packets.

MitigationApply Juniper-provided patches by upgrading to fixed versions (21.1R3-S5, 21.2R3-S2, 21.3R3-S2, 21.4R3, 22.1R3, 22.2R2 or later). Consider implementing BGP MD5 authentication and TTL security as interim mitigations to limit exposure.

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
Junos Os EvolvedOperating system
Affected:= 21.1= 21.2= 21.3= 21.4= 22.1= 22.2
JunosOperating system
Affected:= 21.1= 21.2= 21.3= 21.4= 22.1= 22.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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 installed Junos OS version
    Execute 'show version' or 'show system information' on the device CLI to retrieve the exact Junos version string
    Affected if The version displayed matches 21.1, 21.2, 21.3, 21.4, 22.1, or 22.2 exactly (no later S-series or R-series patch applied)
  2. Confirm BGP is configured
    Execute 'show bgp summary' or review the configuration with 'show configuration protocols bgp' to see if BGP is enabled
    Affected if BGP is actively configured on the device (any BGP neighbor or peer group is present)
  3. Identify BGP peer trust boundary
    Review BGP peer configuration under 'show configuration protocols bgp' to determine if peers are from trusted networks only
    Affected if BGP accepts connections from untrusted or internet-facing peers without additional authentication filters

The device is affected if it runs Junos OS or Junos OS Evolved versions 21.1 through 22.2 and has BGP enabled with exposure to untrusted network peers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Juniper-provided patches by upgrading to fixed versions (21.1R3-S5, 21.2R3-S2, 21.3R3-S2, 21.4R3, 22.1R3, 22.2R2 or later). Consider implementing BGP MD5 authentication and TTL security as interim mitigations to limit exposure.

Recommended fix High confidence

21.1R3-S5, 21.2R3-S2, 21.3R3-S2, 21.4R3, 22.1R3, 22.2R2 or later (EVO: 21.4R3-EVO, 22.1R3-EVO, 22.2R2-EVO or later)

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Determine the appropriate fixed release based on the current major version branch (21.1.x → 21.1R3-S5 or later, 21.2.x → 21.2R3-S2 or later, etc.)
  3. 3. Download the corresponding fixed release from the Juniper Networks support portal
  4. 4. Plan maintenance window as upgrade will require device reboot
  5. 5. Upload the Junos upgrade package to the device using 'file copy' or USB
  6. 6. Initiate the upgrade using 'request system software add <package> reboot'
  7. 7. After reboot, verify the new version with 'show version' and confirm BGP is operational with 'show bgp summary'
  8. 8. For Junos OS Evolved, use 'request system software add <package> reboot' with the EVO image
Caveat Standard Junos upgrade may cause brief routing disruption during reboot; test upgrade in lab first

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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