CVE-2017-10604

Junos OS: SRX Series: Cluster configuration sync failures occur if the root user account is locked out

Description

When the device is configured to perform account lockout with a defined period of time, any unauthenticated user attempting to log in as root with an incorrect password can trigger a lockout of the root account. When an SRX Series device is in cluster mode, and a cluster sync or failover operation occurs, then there will be errors associated with synch or failover while the root account is locked out. Administrators can confirm if the root account is locked out via the following command root@device> show system login lockout user root User Lockout start Lockout end root 1995-01-01 01:00:01 PDT 1995-11-01 01:31:01 PDT Affected releases are Juniper Networks Junos OS 12.1X46 prior to 12.1X46-D65 on SRX series; 12.3X48 prior to 12.3X48-D45 on SRX series; 15.1X49 prior to 15.1X49-D75 on SRX series.

Remediation

Workaround:

  • The lockout feature does not impact console access for the root account. Administrators may login via console, and block the offending incoming traffic which is causing the root account from being locked out via SSH connection attempts to restore cluster sync services from erroring or failing. Administrators may block the offending SSH traffic from an upstream device. Use access lists or firewall filters to limit access to the device only from trusted administrative hosts, networks and users.

Category

5.3
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.34%
Vendor Advisory juniper.net
Affected: Juniper Networks Junos OS
Published at:
Updated at:

References

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

Frequently Asked Questions

What is the severity of CVE-2017-10604?
CVE-2017-10604 has been scored as a medium severity vulnerability.
How to fix CVE-2017-10604?
As a workaround for remediating CVE-2017-10604: The lockout feature does not impact console access for the root account. Administrators may login via console, and block the offending incoming traffic which is causing the root account from being locked out via SSH connection attempts to restore cluster sync services from erroring or failing. Administrators may block the offending SSH traffic from an upstream device. Use access lists or firewall filters to limit access to the device only from trusted administrative hosts, networks and users.
Is CVE-2017-10604 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-10604 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-10604?
CVE-2017-10604 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.