title: Junos OS: vMX: Default credentials supplied in vMX configuration
description: The factory configuration for vMX installations, as shipped, includes default credentials for the root account. Without proper modification of these default credentials by the administrator, an attacker could exploit these credentials and access the vMX instance without authorization. This issue affects Juniper Networks Junos OS: 17.1 versions prior to 17.1R2-S11, 17.1R3-S2 on vMX; 17.2 versions prior to 17.2R3-S3 on vMX; 17.3 versions prior to 17.3R2-S5, 17.3R3-S7 on vMX; 17.4 versions prior to 17.4R2-S9, 17.4R3 on vMX; 18.1 versions prior to 18.1R3-S9 on vMX; 18.2 versions prior to 18.2R2-S7, 18.2R3-S3 on vMX; 18.2X75 versions prior to 18.2X75-D420, 18.2X75-D60 on vMX; 18.3 versions prior to 18.3R1-S7, 18.3R2-S3, 18.3R3-S1 on vMX; 18.4 versions prior to 18.4R1-S5, 18.4R2-S3, 18.4R3 on vMX; 19.1 versions prior to 19.1R1-S4, 19.1R2, 19.1R3 on vMX; 19.2 versions prior to 19.2R1-S3, 19.2R2 on vMX; 19.3 versions prior to 19.3R1-S1, 19.3R2 on vMX.
problem types: CWE-798 Use of Hard-coded Credentials
affected:
{
platforms: vMX
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 17.1R2-S11, 17.1R3-S2, status: affected, version: 17.1, versionType: custom
lessThan: 17.2R3-S3, status: affected, version: 17.2, versionType: custom
lessThan: 17.3R2-S5, 17.3R3-S7, status: affected, version: 17.3, versionType: custom
lessThan: 17.4R2-S9, 17.4R3, status: affected, version: 17.4, versionType: custom
lessThan: 18.1R3-S9, status: affected, version: 18.1, versionType: custom
lessThan: 18.2R2-S7, 18.2R3-S3, status: affected, version: 18.2, versionType: custom
lessThan: 18.2X75-D420, 18.2X75-D60, status: affected, version: 18.2X75, versionType: custom
lessThan: 18.3R1-S7, 18.3R2-S3, 18.3R3-S1, status: affected, version: 18.3, versionType: custom
lessThan: 18.4R1-S5, 18.4R2-S3, 18.4R3, status: affected, version: 18.4, versionType: custom
lessThan: 19.1R1-S4, 19.1R2, 19.1R3, status: affected, version: 19.1, versionType: custom
lessThan: 19.2R1-S3, 19.2R2, status: affected, version: 19.2, versionType: custom
lessThan: 19.3R1-S1, 19.3R2, status: affected, version: 19.3, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 9.8
baseSeverity: CRITICAL
confidentialityImpact: HIGH
integrityImpact: HIGH
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
version: 3.1
]
exploits: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
solutions: The following software releases have been updated to resolve this specific issue: 17.1R2-S11, 17.1R3-S2, 17.2R3-S3, 17.3R2-S5, 17.3R3-S7, 17.4R2-S9, 17.4R3, 18.1R3-S9, 18.2R2-S7, 18.2R3-S3, 18.2X75-D420, 18.2X75-D60, 18.3R1-S7, 18.3R2-S3, 18.3R3-S1, 18.4R1-S5, 18.4R2-S3, 18.4R3, 19.1R1-S4, 19.1R2, 19.1R3, 19.2R1-S3, 19.2R2, 19.3R1-S1, 19.3R2, 19.4R1, and all subsequent releases.
workarounds: Security best practices recommend that the root password be configured on any newly installed vMX instance prior to deployment.