dbcve.org
JunosOperating system · Juniper

CVE-2024-30394

HIGH · 7.5 CVSS v3.1 Published 2024-04-12
Fix available
A fix is available. Upgrade to 21.2 / 21.4 or later.
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 Stack-based Buffer Overflow vulnerability in the Routing Protocol Daemon (RPD) component of Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause an rpd crash, leading to Denial of Service (DoS). On all Junos OS and Junos OS Evolved platforms, when EVPN is configured, and a specific EVPN type-5 route is received via BGP, rpd crashes and restarts. Continuous receipt of this specific route will lead to a sustained Denial of Service (DoS) condition. This issue affects: Junos OS: * all versions before 21.2R3-S7, * from 21.4 before 21.4R3-S5, * from 22.1 before 22.1R3-S4, * from 22.2 before 22.2R3-S2, * from 22.3 before 22.3R3-S1, * from 22.4 before 22.4R3, * from 23.2 before 23.2R2. Junos OS Evolved: * all versions before 21.4R3-S5-EVO, * from 22.1-EVO before 22.1R3-S4-EVO, * from 22.2-EVO before 22.2R3-S2-EVO, * from 22.3-EVO before 22.3R3-S1-EVO, * from 22.4-EVO before 22.4R3-EVO, * from 23.2-EVO before 23.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

A stack-based buffer overflow in the Routing Protocol Daemon (RPD) in Junos OS/Evolved allows an unauthenticated network attacker to crash rpd by sending a specific EVPN type-5 route via BGP when EVPN is configured. This causes rpd to restart, and continuous exploitation leads to sustained DoS.

MitigationUpgrade Junos OS/Evolved to the fixed versions specified in the advisory (21.2R3-S7, 21.4R3-S5, 22.1R3-S4, 22.2R3-S2, 22.3R3-S1, 22.4R3, 23.2R2 or later). Limit BGP peering to trusted sources as a defense-in-depth measure until upgrades can be completed.

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.4= 22.1= 22.2= 22.3= 22.4= 23.2
Junos Os EvolvedOperating system
Affected:< 21.4= 21.4= 22.1= 22.2= 22.3= 22.4= 23.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. Identify the Junos OS/Evolved version
    Run 'show version' on the device CLI to obtain the installed software version
    Affected if The version matches one of the affected ranges: Junos OS versions < 21.2, = 21.2, = 21.4, = 22.1, = 22.2, = 22.3, = 22.4, = 23.2, or Junos OS Evolved versions < 21.4, = 21.4, = 22.1, = 22.2, = 22.3, = 22.4, = 23.2
  2. Verify if EVPN is configured
    Run 'show configuration protocols evpn' or 'show configuration | match evpn' to check for EVPN configuration on the device
    Affected if EVPN is configured and the device is running an affected Junos OS/Evolved version from step 1
  3. Confirm BGP is configured with EVPN address family
    Run 'show bgp summary' or check the BGP configuration under 'protocols bgp' for EVPN family settings (family evpn)
    Affected if BGP is configured to accept EVPN address family routes and the device runs an affected version with EVPN enabled
  4. Check for EVPN type-5 route handling capability
    Run 'show evpn database' or 'show configuration routing-instances' to see if EVPN instances with type-5 routing are configured
    Affected if EVPN type-5 routes are being processed and the device is on an affected version

A device is affected if it runs a vulnerable Junos OS/Evolved version and has EVPN configured with BGP peering, as the vulnerability triggers when receiving a specifically crafted EVPN type-5 route via BGP.

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 / 21.4 or later
Fixed in 21.221.4
Interim mitigation

Upgrade Junos OS/Evolved to the fixed versions specified in the advisory (21.2R3-S7, 21.4R3-S5, 22.1R3-S4, 22.2R3-S2, 22.3R3-S1, 22.4R3, 23.2R2 or later). Limit BGP peering to trusted sources as a defense-in-depth measure until upgrades can be completed.

Recommended fix High confidence

Junos OS: 21.2R3-S7, 21.4R3-S5, 22.1R3-S4, 22.2R3-S2, 22.3R3-S1, 22.4R3, or 23.2R2 (or later). Junos OS Evolved: 21.4R3-S5-EVO, 22.1R3-S4-EVO, 22.2R3-S2-EVO, 22.3R3-S1-EVO, 22.4R3-EVO, or 23.2R2-EVO (or later).

  1. 1. Identify the current Junos OS or Junos OS Evolved version installed on the device using 'show version'
  2. 2. Determine which version branch is currently running (e.g., 21.2, 21.4, 22.1, 22.2, 22.3, 22.4, or 23.2)
  3. 3. For Junos OS: upgrade to the appropriate fixed version based on your current branch: 21.2 branch -> 21.2R3-S7, 21.4 branch -> 21.4R3-S5, 22.1 branch -> 22.1R3-S4, 22.2 branch -> 22.2R3-S2, 22.3 branch -> 22.3R3-S1, 22.4 branch -> 22.4R3, 23.2 branch -> 23.2R2
  4. 4. For Junos OS Evolved: upgrade to the appropriate fixed version: 21.4-EVO -> 21.4R3-S5-EVO, 22.1-EVO -> 22.1R3-S4-EVO, 22.2-EVO -> 22.2R3-S2-EVO, 22.3-EVO -> 22.3R3-S1-EVO, 22.4-EVO -> 22.4R3-EVO, 23.2-EVO -> 23.2R2-EVO
  5. 5. Schedule maintenance window as upgrade requires system reboot
  6. 6. Download the appropriate upgrade package from Juniper Networks support portal
  7. 7. Upload the upgrade package to the device and initiate the upgrade
  8. 8. Verify the upgrade completed successfully and rpd is running using 'show routing-instance' and 'show system processes routing'
Caveat Standard Junos upgrade considerations apply - review release notes for any configuration changes or migration requirements between major releases.

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

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,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 $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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