Junos OS (SRX firewalls)

CVE-2024-30382: RPD crash when CoS-based forwarding (CBF) policy is configured

An Improper Handling of Exceptional Conditions vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based, unauthenticated attacker to send a specific routing update, causing an rpd core due to memory corruption, leading to a Denial of Service (DoS).

Published

ExploitedNot in CISA KEV
Ransomware useNot reportedPer CISA
SeverityHIGHCVSS 4.0 8.7
EPSS0.71%Chance of exploitation in 30 days
Public exploitNot tracked
FixAvailable

Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.

Affected and fixed versions

Product / branchFixed in
Junos OS 020.4R3-S10 or later
Junos OS 21.221.2R3-S8 or later
Junos OS 21.321.3R3 or later
Junos OS 21.421.4R3 or later
Junos OS 22.122.1R2 or later
Junos OS Evolved 021.2R3-S8-EVO or later
Junos OS Evolved 21.321.3R3-EVO or later
Junos OS Evolved 21.421.4R3-EVO or later
Junos OS Evolved 22.122.1R2-EVO or later

Always confirm against the vendor advisory, which lists every fixed hotfix.

What it is

An Improper Handling of Exceptional Conditions vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based, unauthenticated attacker to send a specific routing update, causing an rpd core due to memory corruption, leading to a Denial of Service (DoS).

This issue can only be triggered when the system is configured for CoS-based forwarding (CBF) with a policy map containing a cos-next-hop-map action (see below). This issue affects: Junos OS:

  • all versions before 20.4R3-S10,
  • from 21.2 before 21.2R3-S8,
  • from 21.3 before 21.3R3,
  • from 21.4 before 21.4R3,
  • from 22.1 before 22.1R2;

Junos OS Evolved:

  • all versions before 21.2R3-S8-EVO,
  • from 21.3 before 21.3R3-EVO,
  • from 21.4 before 21.4R3-EVO,
  • from 22.1 before 22.1R2-EVO.

Am I affected?

The following is an example of CoS-based forwarding configuration:

[edit policy-options] set policy-statement my-cos-forwarding term 1 from route-filter destination-prefix match-type set policy-statement my-cos-forwarding term 1 then cos-next-hop-map map-name

Workarounds

There are no known workarounds for this issue.

Exploitation

Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

Sources

KEV status, EPSS score and vendor data refreshed automatically, last on 13 Oct 2026.

Get alerts

A notification when we publish a new analysis or a covered vendor gets a new actively exploited CVE. No account, no email.