CVE-2025-30645: CWE-476 NULL Pointer Dereference in Juniper Networks Junos OS
A NULL Pointer Dereference vulnerability in the flow daemon (flowd) of Juniper Networks Junos OS on SRX Series allows an attacker causing specific, valid control traffic to be sent out of a Dual-Stack (DS) Lite tunnel to crash the flowd process, resulting in a Denial of Service (DoS). Continuous triggering of specific control traffic will create a sustained Denial of Service (DoS) condition. On all SRX platforms, when specific, valid control traffic needs to be sent out of a DS-Lite tunnel, a segmentation fault occurs within the flowd process, resulting in a network outage until the flowd process restarts. This issue affects Junos OS on SRX Series: * All versions before 21.2R3-S9, * from 21.4 before 21.4R3-S9, * from 22.2 before 22.2R3-S5, * from 22.4 before 22.4R3-S6, * from 23.2 before 23.2R2-S3, * from 23.4 before 23.4R2.
AI Analysis
Technical Summary
CVE-2025-30645 is a vulnerability identified in the flow daemon (flowd) component of Juniper Networks Junos OS running on SRX Series devices. The flaw is a NULL Pointer Dereference (CWE-476) that occurs when specific, valid control traffic is sent out of a Dual-Stack Lite (DS-Lite) tunnel. This causes the flowd process to crash due to a segmentation fault, resulting in a Denial of Service (DoS) condition. The vulnerability affects multiple versions of Junos OS on SRX platforms, specifically all versions before 21.2R3-S9, and certain builds from 21.4, 22.2, 22.4, 23.2, and 23.4 branches before their respective patch releases. The impact is a network outage until the flowd process restarts, and continuous triggering of the specific control traffic can sustain the DoS condition. The vulnerability does not require authentication or user interaction, but it requires the attacker to send crafted control traffic through the DS-Lite tunnel. No known exploits are currently reported in the wild, and no official patches are linked yet. The issue is rooted in improper handling of control traffic within the DS-Lite tunneling mechanism, which is used to facilitate IPv4 connectivity over IPv6 networks. The flowd process is critical for managing network flows on SRX devices, so its crash leads to disruption of network traffic and potential loss of availability for services relying on these devices.
Potential Impact
For European organizations, especially those relying on Juniper SRX Series firewalls and routers for network security and traffic management, this vulnerability poses a significant risk of network disruption. The DoS condition can lead to temporary loss of connectivity, impacting business operations, critical infrastructure, and service availability. Organizations using DS-Lite tunnels to support IPv4 over IPv6 transition mechanisms are particularly vulnerable. This can affect ISPs, telecom providers, and enterprises with dual-stack deployments. The sustained DoS could be exploited by attackers to disrupt services during critical periods or as part of a larger attack campaign. Given the reliance on Juniper SRX devices in many European telecom networks and data centers, the vulnerability could affect a broad range of sectors including finance, government, healthcare, and industrial control systems. The inability to process control traffic correctly could also complicate incident response and network troubleshooting during an attack or failure event.
Mitigation Recommendations
1. Immediate mitigation should include monitoring network traffic for unusual or repeated DS-Lite control traffic patterns that could trigger the vulnerability. 2. Implement network segmentation and filtering to restrict untrusted sources from sending DS-Lite control traffic to SRX devices. 3. Where possible, temporarily disable DS-Lite tunneling if it is not critical to operations until patches are available. 4. Apply strict access control lists (ACLs) on interfaces facing untrusted networks to limit exposure. 5. Prepare for rapid restart procedures of the flowd process to minimize downtime if a crash occurs. 6. Engage with Juniper Networks support to obtain early access to patches or workarounds as they become available. 7. Conduct thorough testing of updated Junos OS versions in a controlled environment before deployment. 8. Maintain up-to-date backups of device configurations to enable quick recovery. 9. Enhance network monitoring and alerting specifically for flowd process crashes and related anomalies. 10. Educate network operations teams about this vulnerability and response procedures to reduce mean time to recovery.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden, Poland, Belgium, Finland
CVE-2025-30645: CWE-476 NULL Pointer Dereference in Juniper Networks Junos OS
Description
A NULL Pointer Dereference vulnerability in the flow daemon (flowd) of Juniper Networks Junos OS on SRX Series allows an attacker causing specific, valid control traffic to be sent out of a Dual-Stack (DS) Lite tunnel to crash the flowd process, resulting in a Denial of Service (DoS). Continuous triggering of specific control traffic will create a sustained Denial of Service (DoS) condition. On all SRX platforms, when specific, valid control traffic needs to be sent out of a DS-Lite tunnel, a segmentation fault occurs within the flowd process, resulting in a network outage until the flowd process restarts. This issue affects Junos OS on SRX Series: * All versions before 21.2R3-S9, * from 21.4 before 21.4R3-S9, * from 22.2 before 22.2R3-S5, * from 22.4 before 22.4R3-S6, * from 23.2 before 23.2R2-S3, * from 23.4 before 23.4R2.
AI-Powered Analysis
Technical Analysis
CVE-2025-30645 is a vulnerability identified in the flow daemon (flowd) component of Juniper Networks Junos OS running on SRX Series devices. The flaw is a NULL Pointer Dereference (CWE-476) that occurs when specific, valid control traffic is sent out of a Dual-Stack Lite (DS-Lite) tunnel. This causes the flowd process to crash due to a segmentation fault, resulting in a Denial of Service (DoS) condition. The vulnerability affects multiple versions of Junos OS on SRX platforms, specifically all versions before 21.2R3-S9, and certain builds from 21.4, 22.2, 22.4, 23.2, and 23.4 branches before their respective patch releases. The impact is a network outage until the flowd process restarts, and continuous triggering of the specific control traffic can sustain the DoS condition. The vulnerability does not require authentication or user interaction, but it requires the attacker to send crafted control traffic through the DS-Lite tunnel. No known exploits are currently reported in the wild, and no official patches are linked yet. The issue is rooted in improper handling of control traffic within the DS-Lite tunneling mechanism, which is used to facilitate IPv4 connectivity over IPv6 networks. The flowd process is critical for managing network flows on SRX devices, so its crash leads to disruption of network traffic and potential loss of availability for services relying on these devices.
Potential Impact
For European organizations, especially those relying on Juniper SRX Series firewalls and routers for network security and traffic management, this vulnerability poses a significant risk of network disruption. The DoS condition can lead to temporary loss of connectivity, impacting business operations, critical infrastructure, and service availability. Organizations using DS-Lite tunnels to support IPv4 over IPv6 transition mechanisms are particularly vulnerable. This can affect ISPs, telecom providers, and enterprises with dual-stack deployments. The sustained DoS could be exploited by attackers to disrupt services during critical periods or as part of a larger attack campaign. Given the reliance on Juniper SRX devices in many European telecom networks and data centers, the vulnerability could affect a broad range of sectors including finance, government, healthcare, and industrial control systems. The inability to process control traffic correctly could also complicate incident response and network troubleshooting during an attack or failure event.
Mitigation Recommendations
1. Immediate mitigation should include monitoring network traffic for unusual or repeated DS-Lite control traffic patterns that could trigger the vulnerability. 2. Implement network segmentation and filtering to restrict untrusted sources from sending DS-Lite control traffic to SRX devices. 3. Where possible, temporarily disable DS-Lite tunneling if it is not critical to operations until patches are available. 4. Apply strict access control lists (ACLs) on interfaces facing untrusted networks to limit exposure. 5. Prepare for rapid restart procedures of the flowd process to minimize downtime if a crash occurs. 6. Engage with Juniper Networks support to obtain early access to patches or workarounds as they become available. 7. Conduct thorough testing of updated Junos OS versions in a controlled environment before deployment. 8. Maintain up-to-date backups of device configurations to enable quick recovery. 9. Enhance network monitoring and alerting specifically for flowd process crashes and related anomalies. 10. Educate network operations teams about this vulnerability and response procedures to reduce mean time to recovery.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- juniper
- Date Reserved
- 2025-03-24T19:34:11.320Z
- Cisa Enriched
- true
Threat ID: 682d983fc4522896dcbf0925
Added to database: 5/21/2025, 9:09:19 AM
Last enriched: 6/24/2025, 9:25:33 AM
Last updated: 8/16/2025, 12:21:24 AM
Views: 15
Related Threats
CVE-2025-9092: CWE-400 Uncontrolled Resource Consumption in Legion of the Bouncy Castle Inc. Bouncy Castle for Java - BC-FJA 2.1.0
LowCVE-2025-9089: Stack-based Buffer Overflow in Tenda AC20
HighCVE-2025-9088: Stack-based Buffer Overflow in Tenda AC20
HighCVE-2025-9087: Stack-based Buffer Overflow in Tenda AC20
HighCVE-2025-8878: CWE-94 Improper Control of Generation of Code ('Code Injection') in properfraction Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.