dbcve.org
JunosOperating system · Juniper

CVE-2017-10604

MEDIUM · 5.3 CVSS v3.0 Published 2017-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A logic flaw in Junos OS account lockout handling allows any unauthenticated user to lock out the root account by simply attempting to log in with an incorrect password. When SRX Series devices are in cluster mode, this root account lockout causes errors during cluster sync or failover operations due to the root account being unavailable.

MitigationUpgrade Junos OS to version 12.1X46-D65 or later, 12.3X48-D45 or later, or 15.1X49-D75 or later. Consider disabling root account lockout or using certificate-based authentication as a workaround until the upgrade can be performed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:= 12.1x46= 12.3x48= 15.1x49

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Junos OS version
    Execute 'show version' on the device CLI to retrieve the installed Junos version and build number
    Affected if The version is 12.1X46 before build D65, 12.3X48 before build D45, or 15.1X49 before build D75
  2. Confirm the device is an SRX Series model
    Execute 'show chassis hardware' or 'show system information' to identify the device model
    Affected if The device is an SRX Series firewall (SRX100, SRX110, SRX210, SRX220, SRX240, SRX340, SRX345, SRX550, SRX650, or similar)
  3. Determine if chassis cluster mode is enabled
    Execute 'show chassis cluster status' to check cluster configuration and status
    Affected if The device shows active cluster membership with a peer node (redundancy group 0 and/or higher is configured)
  4. Verify root account lockout policy configuration
    Execute 'show system login' and look for 'lockout' or 'retry' related configuration under the [system login] hierarchy
    Affected if Root account lockout is enabled (default behavior locks the root account after failed login attempts)

A user is affected if they are running a vulnerable Junos version (pre-D65/D45/D75) on an SRX Series device with chassis cluster enabled and root account lockout configured, as unauthenticated attackers can trigger root lockout causing cluster sync or failover failures.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS to version 12.1X46-D65 or later, 12.3X48-D45 or later, or 15.1X49-D75 or later. Consider disabling root account lockout or using certificate-based authentication as a workaround until the upgrade can be performed.

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-10604 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-10604 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data