dbcve.org
JunosOperating system · Juniper

CVE-2024-30395

HIGH · 7.5 CVSS v3.1 Published 2024-04-12
Fix available
A fix is available. Upgrade to 21.2 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
An Improper Validation of Specified Type of Input vulnerability in Routing Protocol Daemon (RPD) of Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause Denial of Service (DoS). If a BGP update is received over an established BGP session which contains a tunnel encapsulation attribute with a specifically malformed TLV, rpd will crash and restart. This issue affects: Junos OS: * all versions before 21.2R3-S7,  * from 21.3 before 21.3R3-S5,  * from 21.4 before 21.4R3-S5,  * from 22.1 before 22.1R3-S5,  * from 22.2 before 22.2R3-S3,  * from 22.3 before 22.3R3-S2,  * from 22.4 before 22.4R3,  * from 23.2 before 23.2R1-S2, 23.2R2. Junos OS Evolved: * all versions before 21.2R3-S7-EVO,  * from 21.3-EVO before 21.3R3-S5-EVO,  * from 21.4-EVO before 21.4R3-S5-EVO,  * from 22.2-EVO before 22.2R3-S3-EVO,  * from 22.3-EVO before 22.3R3-S2-EVO,  * from 22.4-EVO before 22.4R3-EVO,  * from 23.2-EVO before 23.2R1-S2-EVO, 23.2R2-EVO. This is a related but separate issue than the one described in JSA75739

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

Improper validation vulnerability in Junos OS RPD allows an unauthenticated attacker to crash the routing daemon by sending a BGP update with a malformed tunnel encapsulation attribute TLV over an established BGP session. This causes rpd to crash and restart, resulting in denial of service.

MitigationApply the appropriate Junos OS or Junos OS Evolved software update from the fixed versions listed (21.2R3-S7, 21.3R3-S5, 21.4R3-S5, 22.1R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R3, or 23.2R1-S2/23.2R2) to remediate this vulnerability.

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= 23.2
Junos Os EvolvedOperating system
Affected:< 21.2= 21.2= 21.3= 21.4= 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 Junos platform and version
    Run 'show version' or 'show version detail' to confirm whether the device runs Junos OS or Junos OS Evolved and note the exact version string (for example, 21.4R1-S2.3)
    Affected if The device runs Junos OS or Junos OS Evolved and the version matches the affected ranges: any version less than 21.2, or exactly 21.2, 21.3, 21.4, 22.1, 22.2, 22.3, 22.4, or 23.2 (without the available Sx补丁 or R2 update)
  2. Confirm BGP is configured
    Run 'show configuration protocols bgp' to see if BGP is configured under the protocols hierarchy
    Affected if BGP is actively configured on the device; the vulnerability requires BGP to be enabled for the malformed update to be processed
  3. Verify established BGP peers exist
    Run 'show bgp summary' or 'show bgp neighbor' to list active BGP peer sessions
    Affected if There are established BGP peers; the attacker must send the malformed update over an existing BGP session to trigger the crash

The device is affected if it runs a vulnerable Junos OS or Junos OS Evolved version AND has BGP configured with active peers, making it reachable to an attacker with BGP session access.

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 appropriate Junos OS or Junos OS Evolved software update from the fixed versions listed (21.2R3-S7, 21.3R3-S5, 21.4R3-S5, 22.1R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R3, or 23.2R1-S2/23.2R2) to remediate this vulnerability.

Recommended fix High confidence

Upgrade to one of the fixed releases: 21.2R3-S7, 21.3R3-S5, 21.4R3-S5, 22.1R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R3, 23.2R1-S2, or 23.2R2 (or corresponding -EVO versions for Junos OS Evolved)

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Review the fixed version list and determine the appropriate upgrade target based on your current release train
  3. 3. Schedule a maintenance window as the upgrade will require a system reload
  4. 4. Download the appropriate fixed Junos software image (21.2R3-S7, 21.3R3-S5, 21.4R3-S5, 22.1R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R3, 23.2R1-S2, or 23.2R2 for Junos OS; or corresponding -EVO versions for Junos OS Evolved) from Juniper Networks support portal
  5. 5. Upload the software package to the device using 'file copy' or USB transfer
  6. 6. Install the software using 'request system software add <package> reboot' command
  7. 7. After the device reboots, verify the new version is running with 'show version'
  8. 8. Verify BGP peering is stable and rpd process is running normally using 'show bgp summary' and 'show system processes routing'
Caveat Standard Junos 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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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