title: Junos OS: Insufficient authentication for user login when a specific system configuration error occurs.
description: A specific device configuration can result in a commit failure condition. When this occurs, a user is logged in without being prompted for a password while trying to login through console, ssh, ftp, telnet or su, etc., This issue relies upon a device configuration precondition to occur. Typically, device configurations are the result of a trusted administrative change to the system's running configuration. The following error messages may be seen when this failure occurs: mgd: error: commit failed: (statements constraint check failed) Warning: Commit failed, activating partial configuration. Warning: Edit the router configuration to fix these errors. If the administrative changes are not made that result in such a failure, then this issue is not seen. No other Juniper Networks products or platforms are affected by this issue. Affected releases are Juniper Networks Junos OS 12.3 prior to 12.3R10, 12.3R11; 12.3X48 prior to 12.3X48-D20; 13.2 prior to 13.2R8; 13.3 prior to 13.3R7; 14.1 prior to 14.1R4-S12, 14.1R5, 14.1R6; 14.1X53 prior to 14.1X53-D30; 14.2 prior to 14.2R4; 15.1 prior to 15.1F2, 15.1F3, 15.1R2.
problem types: authentication bypass vulnerability
affected:
{
product: Junos OS
vendor: Juniper Networks
versions:
status: affected, version: 12.3 prior to 12.3R10, 12.3R11
status: affected, version: 12.3X48 prior to 12.3X48-D20
status: affected, version: 13.2 prior to 13.2R8
status: affected, version: 13.3 prior to 13.3R7
status: affected, version: 14.1 prior to 14.1R4-S12, 14.1R5, 14.1R6
status: affected, version: 14.1X53 prior to 14.1X53-D30
status: affected, version: 14.2 prior to 14.2R4
status: affected, version: 15.1 prior to 15.1F2, 15.1F3, 15.1R2
}
metrics:
cvssV3_0: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 9.8
baseSeverity: CRITICAL
confidentialityImpact: HIGH
integrityImpact: HIGH
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
version: 3.0
]
workarounds: Make sure authentication works as expected after a system configuration change.
Use the SSH certificate based authentication.
Use access lists or firewall filters to limit access to the device only from trusted administrative hosts, networks and users.