CVE-2017-10601

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.

Remediation

Workaround:

  • 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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.42%
Vendor Advisory juniper.net
Affected: Juniper Networks Junos OS
Published at:
Updated at:

References

Link Tags
https://kb.juniper.net/JSA10802 mitigation vendor advisory
http://www.securitytracker.com/id/1038902 vdb entry third party advisory

Frequently Asked Questions

What is the severity of CVE-2017-10601?
CVE-2017-10601 has been scored as a critical severity vulnerability.
How to fix CVE-2017-10601?
As a workaround for remediating CVE-2017-10601: 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.
Is CVE-2017-10601 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-10601 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-10601?
CVE-2017-10601 affects Juniper Networks Junos OS.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.