CVE-2017-10604
Last modified
CVE-2017-10604 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.88% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Juniper | Junos | 12.1x46 |
| Juniper | Junos | 12.3x48 |
| Juniper | Junos | 15.1x49 |
References
- http://www.securitytracker.com/id/1038886Third Party Advisory, VDB Entry
- https://kb.juniper.net/JSA10806Vendor Advisory
- http://www.securitytracker.com/id/1038886Third Party Advisory, VDB Entry
- https://kb.juniper.net/JSA10806Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-10604?
How severe is CVE-2017-10604?
How do I fix CVE-2017-10604?
Are you affected by CVE-2017-10604?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
