A Deadlock vulnerability in the packet forwarding engine (PFE) of Juniper Networks Junos OS on SRX Series allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). When a large amount of traffic is processed by ATP Cloud inspection, a deadlock can occur which will result in a PFE crash and restart. Whether the crash occurs, depends on system internal timing that is outside the attackers control. This issue affects Junos OS on SRX Series: * All versions before 21.3R3-S1, * 21.4 versions before 21.4R3, * 22.1 versions before 22.1R2, * 22.2 versions before 22.2R1-S2, 22.2R2.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.9, indicating it can be exploited remotely over the network but requires specific conditions to be met without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 18 products from juniper, from juniper, from juniper and 15 others, organizations running these solutions should prioritize assessment and patching.
Reported in 2024, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2024-10-11T16:15:12.450
2026-01-26T18:28:54.723
Analyzed
CVSSv3.1: 5.9 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Operating System | juniper | junos | < 21.3 | Yes |
| Operating System | juniper | junos | 21.3 | Yes |
| Operating System | juniper | junos | 21.3 | Yes |
| Operating System | juniper | junos | 21.3 | Yes |
| Operating System | juniper | junos | 21.3 | Yes |
| Operating System | juniper | junos | 21.3 | Yes |
| Operating System | juniper | junos | 21.3 | Yes |
| Operating System | juniper | junos | 21.3 | Yes |
| Operating System | juniper | junos | 21.3 | Yes |
| Operating System | juniper | junos | 21.4 | Yes |
| Operating System | juniper | junos | 21.4 | Yes |
| Operating System | juniper | junos | 21.4 | Yes |
| Operating System | juniper | junos | 21.4 | Yes |
| Operating System | juniper | junos | 21.4 | Yes |
| Operating System | juniper | junos | 21.4 | Yes |
| Operating System | juniper | junos | 21.4 | Yes |
| Operating System | juniper | junos | 22.1 | Yes |
| Operating System | juniper | junos | 22.1 | Yes |
| Operating System | juniper | junos | 22.1 | Yes |
| Operating System | juniper | junos | 22.1 | Yes |
| Operating System | juniper | junos | 22.2 | Yes |
| Operating System | juniper | junos | 22.2 | Yes |
| Operating System | juniper | junos | 22.2 | Yes |
| Operating System | juniper | junos | 22.2 | Yes |
| Hardware | juniper | srx1500 | - | No |
| Hardware | juniper | srx1600 | - | No |
| Hardware | juniper | srx2300 | - | No |
| Hardware | juniper | srx300 | - | No |
| Hardware | juniper | srx320 | - | No |
| Hardware | juniper | srx340 | - | No |
| Hardware | juniper | srx345 | - | No |
| Hardware | juniper | srx380 | - | No |
| Hardware | juniper | srx4100 | - | No |
| Hardware | juniper | srx4120 | - | No |
| Hardware | juniper | srx4200 | - | No |
| Hardware | juniper | srx4300 | - | No |
| Hardware | juniper | srx4600 | - | No |
| Hardware | juniper | srx4700 | - | No |
| Hardware | juniper | srx5400 | - | No |
| Hardware | juniper | srx5600 | - | No |
| Hardware | juniper | srx5800 | - | No |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For juniper's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.