CVE-2020-1614
10.0 · CRITICALOverview
CVE-2020-1614 is a critical-severity vulnerability affecting juniper junos. It was published on April 8, 2020 and has a CVSS 3.1 base score of 10.0 (CRITICAL).
This vulnerability has a CVSS 3.1 base score of 10.0, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
Technical Description
A Use of Hard-coded Credentials vulnerability exists in the NFX250 Series for the vSRX Virtual Network Function (VNF) instance, which allows an attacker to take control of the vSRX VNF instance if they have the ability to access an administrative service (e.g. SSH) on the VNF, either locally, or through the network. This issue only affects the NFX250 Series vSRX VNF. No other products or platforms are affected. This issue is only applicable to environments where the vSRX VNF root password has not been configured. This issue affects the Juniper Networks NFX250 Network Services Platform vSRX VNF instance on versions prior to 19.2R1.
Remediation
Check the references section for vendor advisories and patches from juniper. Update junos to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| juniper | junos | >= 0, < 19.2 | Affected |
References
Frequently Asked Questions
What is CVE-2020-1614?
CVE-2020-1614 is a critical-severity vulnerability affecting juniper junos. It was published on April 8, 2020 and has a CVSS 3.1 base score of 10.0 (CRITICAL).
How severe is CVE-2020-1614?
This vulnerability has a CVSS 3.1 base score of 10.0, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
How do I fix or remediate CVE-2020-1614?
Check the references section for vendor advisories and patches from juniper. Update junos to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2020-1614?
CyberStrike's AI-powered security agents can automatically detect CVE-2020-1614 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related CRITICAL CVEs from 2020
View all →In ApexPro Telemetry Server, Versions 4.2 and prior, CARESCAPE Telemetry Server v4.2 & prior, Clinic
In ApexPro Telemetry Server, Versions 4.2 and prior, CARESCAPE Telemetry Server v4.2 & prior, Clinic
In ApexPro Telemetry Server Versions 4.2 and prior, CARESCAPE Telemetry Server v4.2 & prior, Clinica
In ApexPro Telemetry Server Versions 4.2 and prior, CARESCAPE Telemetry Server v4.2 & prior, Clinica
Missing Authentication for Critical Function in the Bosch Video Streaming Gateway (VSG) allows an un
Deserialization of Untrusted Data in the BVMS Mobile Video Service (BVMS MVS) allows an unauthentica
NaCl in 2015 allowed the CLFLUSH instruction, making rowhammer attacks possible.
A remote code execution vulnerability exists in the way that the Microsoft Server Message Block 3.1.
Apache Commons Configuration uses a third-party library to parse YAML files which by default allows
UltraLog Express device management interface does not properly filter user inputted string in some s
Beaker before 0.8.9 allows a sandbox escape, enabling system access and code execution. This occurs
The Firefox content processes did not sufficiently lockdown access control which could result in a s