CVE-2017-10601: Junos OS: Insufficient authentication for user login when a specific system configuration error occurs.
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-10601?
CVE-2017-10601 has been identified with a moderate severity level due to its potential to allow unauthorized logins without a password prompt.
How do I fix CVE-2017-10601?
To mitigate CVE-2017-10601, it is recommended to review and modify the device configuration that may trigger the vulnerability.
Which software versions are affected by CVE-2017-10601?
CVE-2017-10601 affects multiple versions of Juniper JUNOS, particularly versions 12.3, 13.2, 14.1, and 15.1.
What are the possible risks associated with CVE-2017-10601?
The main risk associated with CVE-2017-10601 is unauthorized access to the system, allowing attackers to bypass authentication mechanisms.
How can I verify if my device is vulnerable to CVE-2017-10601?
To verify if your device is vulnerable to CVE-2017-10601, check the device configuration and consult your system's logs for unusual login behavior.