Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-59964: CWE-908: Use of Uninitialized Resource in Juniper Networks Junos OS

0
High
VulnerabilityCVE-2025-59964cvecve-2025-59964cwe-908
Published: Thu Oct 09 2025 (10/09/2025, 15:46:25 UTC)
Source: CVE Database V5
Vendor/Project: Juniper Networks
Product: Junos OS

Description

A Use of Uninitialized Resource vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on SRX4700 devices allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). When forwarding-options sampling is enabled, receipt of any traffic destined to the Routing Engine (RE) by the PFE line card leads to an FPC crash and restart, resulting in a Denial of Service (DoS). Continued receipt and processing of any traffic leading to the RE by the PFE line card will create a sustained Denial of Service (DoS) condition to the PFE line card. This issue affects Junos OS on SRX4700:  * from 24.4 before 24.4R1-S3, 24.4R2 This issue affects IPv4 and IPv6.

AI-Powered Analysis

AILast updated: 10/09/2025, 16:07:58 UTC

Technical Analysis

CVE-2025-59964 is a vulnerability classified under CWE-908 (Use of Uninitialized Resource) found in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS running on SRX4700 devices. The vulnerability manifests when the forwarding-options sampling feature is enabled. In this state, any network traffic destined for the Routing Engine (RE) that is processed by the PFE line card causes the Flexible PIC Concentrator (FPC) to crash and restart. This results in a Denial of Service (DoS) condition affecting the PFE line card, which can be sustained by continued receipt of such traffic. The vulnerability affects both IPv4 and IPv6 traffic. The flaw exists in Junos OS version 24.4 prior to 24.4R1-S3 and 24.4R2 releases. Exploitation requires no authentication or user interaction and can be triggered remotely over the network, making it easily exploitable. The impact is limited to availability, as confidentiality and integrity are not affected. No public exploits are currently known, but the vulnerability has a CVSS v3.1 base score of 7.5 (high severity), reflecting its potential to disrupt network operations. Juniper has not yet published patches or mitigation guidance at the time of this report.

Potential Impact

For European organizations, especially those operating critical infrastructure, telecommunications, or large enterprise networks using Juniper SRX4700 devices, this vulnerability poses a significant risk to network availability. A successful attack can cause repeated crashes and restarts of the PFE line card, leading to sustained Denial of Service conditions that disrupt traffic forwarding and potentially degrade or halt network services. This can affect business continuity, cause service outages, and impact dependent services such as VPNs, firewalls, and routing functions. Given the vulnerability requires no authentication and can be triggered remotely, attackers can exploit it from outside the network perimeter, increasing the threat surface. The impact is particularly critical for organizations relying on Junos OS 24.4 versions before patched releases. Disruptions in network infrastructure can also have cascading effects on connected systems and services, amplifying operational risks.

Mitigation Recommendations

1. Immediate upgrade to Junos OS versions 24.4R1-S3 or 24.4R2 or later where the vulnerability is addressed. 2. If patching is not immediately possible, disable forwarding-options sampling on SRX4700 devices to prevent triggering the vulnerability. 3. Implement network-level filtering to block or rate-limit traffic destined to the Routing Engine (RE) from untrusted sources, reducing exposure to malicious packets. 4. Monitor device logs and performance metrics for signs of FPC crashes or restarts indicative of exploitation attempts. 5. Employ network segmentation to isolate critical Juniper devices from untrusted networks and restrict access to management interfaces. 6. Engage with Juniper support for any available interim mitigation scripts or configuration recommendations. 7. Conduct regular vulnerability assessments and penetration testing focused on network infrastructure devices to detect exploitation attempts early. 8. Maintain an incident response plan tailored to network device DoS scenarios to minimize downtime.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
juniper
Date Reserved
2025-09-23T18:19:06.955Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68e7da5fba0e608b4fa05bc5

Added to database: 10/9/2025, 3:53:03 PM

Last enriched: 10/9/2025, 4:07:58 PM

Last updated: 10/9/2025, 7:09:47 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats