An Improper Check or Handling of Exceptional Conditions vulnerability in the UTM (Unified Threat Management) Web-Filtering feature of Juniper Networks Junos OS on SRX Series causes a jbuf memory leak to occur when accessing certain websites, eventually leading to a Denial of Service (DoS) condition. Service restoration is only possible by rebooting the system. The jbuf memory leak only occurs in SSL Proxy and UTM Web-Filtering configurations. Other products, platforms, and configurations are not affected by this vulnerability. This issue affects Juniper Networks Junos OS on SRX Series: 22.2 versions prior to 22.2R3; 22.3 versions prior to 22.3R2-S1, 22.3R3; 22.4 versions prior to 22.4R1-S2, 22.4R2. This issue does not affect Juniper Networks Junos OS versions prior to 22.2R2.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.5, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 31 products from juniper, from juniper, from juniper and 28 others, organizations running these solutions should prioritize assessment and patching.
Reported in 2023, 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.
2023-07-14T15:15:08.913
2024-11-21T08:10:41.753
Modified
CVSSv3.1: 7.5 (HIGH)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| 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 |
| Operating System | juniper | junos | 22.2 | Yes |
| Operating System | juniper | junos | 22.2 | Yes |
| Operating System | juniper | junos | 22.3 | Yes |
| Operating System | juniper | junos | 22.3 | Yes |
| Operating System | juniper | junos | 22.3 | Yes |
| Operating System | juniper | junos | 22.3 | Yes |
| Operating System | juniper | junos | 22.4 | Yes |
| Operating System | juniper | junos | 22.4 | Yes |
| Application | juniper | vsrx | - | No |
| Hardware | juniper | csrx | - | No |
| Hardware | juniper | srx100 | - | No |
| Hardware | juniper | srx110 | - | No |
| Hardware | juniper | srx1400 | - | No |
| Hardware | juniper | srx1500 | - | No |
| Hardware | juniper | srx210 | - | No |
| Hardware | juniper | srx220 | - | No |
| Hardware | juniper | srx240 | - | No |
| Hardware | juniper | srx240h2 | - | No |
| Hardware | juniper | srx240m | - | No |
| Hardware | juniper | srx300 | - | No |
| Hardware | juniper | srx320 | - | No |
| Hardware | juniper | srx340 | - | No |
| Hardware | juniper | srx3400 | - | No |
| Hardware | juniper | srx345 | - | No |
| Hardware | juniper | srx3600 | - | No |
| Hardware | juniper | srx380 | - | No |
| Hardware | juniper | srx4000 | - | No |
| Hardware | juniper | srx4100 | - | No |
| Hardware | juniper | srx4200 | - | No |
| Hardware | juniper | srx4600 | - | No |
| Hardware | juniper | srx5000 | - | No |
| Hardware | juniper | srx5400 | - | No |
| Hardware | juniper | srx550 | - | No |
| Hardware | juniper | srx550_hm | - | No |
| Hardware | juniper | srx550m | - | No |
| Hardware | juniper | srx5600 | - | No |
| Hardware | juniper | srx5800 | - | No |
| Hardware | juniper | srx650 | - | 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.