Juniper Junos up to 12.1x46 on SRX Dynamic IPsec VPN Connection denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Juniper Junos 11.4/12.1/12.1x44/12.1x45/12.1x46 on SRX and classified as problematic. Affected is an unknown function of the component Dynamic IPsec VPN Connection Handler. The manipulation leads to denial of service. This vulnerability is traded as CVE-2014-0612. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Juniper Junos 11.4/12.1/12.1x44/12.1x45/12.1x46 on SRX (Router Operating System). It has been rated as problematic. This issue affects an unknown part of the component Dynamic IPsec VPN Connection Handler. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. The summary by CVE is:
Unspecified vulnerability in Juniper Junos before 11.4R10-S1, before 11.4R11, 12.1X44 before 12.1X44-D26, 12.1X44 before 12.1X44-D30, 12.1X45 before 12.1X45-D20, and 12.1X46 before 12.1X46-D10, when Dynamic IPsec VPN is configured, allows remote attackers to cause a denial of service (new Dynamic VPN connection failures and CPU and disk consumption) via unknown vectors.
The weakness was shared 04/09/2014 as JSA10620 / PR 934366 / KB16765 as confirmed advisory (Website). The advisory is shared at kb.juniper.net. The identification of this vulnerability is CVE-2014-0612 since 12/31/2013. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue. The advisory points out:
(...) a remote unauthenticated user may cause a denial of service condition where new Dynamic VPN connections may fail for other users. This issue may also lead to high CPU consumption and disk usage which may cause other complications.
The vulnerability scanner Nessus provides a plugin with the ID 73494 (Juniper Junos SRX Series Dynamic IPsec VPN DoS (JSA10620)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Junos Local Security Checks.
Upgrading to version 11.4R10-S1, 11.4R11, 12.1X44-D26, 12.1X44-D30, 12.1X45-D20 or 12.1X46-D10 eliminates this vulnerability. It is possible to mitigate the problem by applying the configuration setting Disable Dynamic IPsec VPN. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (92398), Tenable (73494), SecurityFocus (BID 66759†), Secunia (SA57845†) and SecurityTracker (ID 1030057†). The entries VDB-12873, VDB-12872, VDB-12871 and VDB-12870 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Juniper Junos SRX100
- Juniper Junos SRX110
- Juniper Junos SRX210
- Juniper Junos SRX220
- Juniper Junos SRX240
- Juniper Junos SRX550
- Juniper Junos SRX650
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.juniper.net/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 73494
Nessus Name: Juniper Junos SRX Series Dynamic IPsec VPN DoS (JSA10620)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Junos 11.4R10-S1/11.4R11/12.1X44-D26/12.1X44-D30/12.1X45-D20/12.1X46-D10
Config: Disable Dynamic IPsec VPN
Timeline
12/31/2013 🔍04/09/2014 🔍
04/09/2014 🔍
04/09/2014 🔍
04/09/2014 🔍
04/10/2014 🔍
04/11/2014 🔍
04/11/2014 🔍
04/14/2014 🔍
04/14/2014 🔍
04/22/2014 🔍
05/10/2026 🔍
Sources
Vendor: juniper.netAdvisory: JSA10620 / PR 934366 / KB16765
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2014-0612 (🔍)
GCVE (CVE): GCVE-0-2014-0612
GCVE (VulDB): GCVE-100-12869
IAVM: 🔍
X-Force: 92398 - Juniper JunOS SRX Branch Series Service Gateways VPN denial of service, Medium Risk
SecurityFocus: 66759 - Juniper Junos Branch SRX Series CVE-2014-0612 Denial of Service Vulnerability
Secunia: 57845 - Juniper JunOS SRX Branch Series Service Gateways Dynamic VPN Connections Denial of Service, Less Critical
SecurityTracker: 1030057 - Juniper Junos Branch SRX Series Dynamic VPN Flaw Lets Remote Authenticated Users Deny Service
Vulnerability Center: 44172 - Juniper Networks Junos Multiple Versions on SRX Series Remote DoS via Unknown Vectors, Medium
See also: 🔍
Entry
Created: 04/11/2014 10:24Updated: 05/10/2026 14:33
Changes: 04/11/2014 10:24 (86), 04/29/2019 07:03 (4), 06/16/2021 19:55 (2), 05/10/2026 14:33 (15)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.