dbcve.org
JunosOperating system · Juniper

CVE-2017-10601

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
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.

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

In Junos OS, a specific device configuration that causes a commit failure (statements constraint check failed) can result in users being logged in without password authentication when accessing via console, ssh, ftp, telnet, or su. This creates an authentication bypass where partial configuration gets activated after the commit fails.

MitigationUpgrade Junos OS to the fixed versions (12.3R10+, 12.3X48-D20+, 13.2R8+, 13.3R7+, 14.1R4-S12+, 14.1X53-D30+, 14.2R4+, 15.1F2+/15.1F3+/15.1R2+) and review configurations for any that may cause commit failures.

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.3= 12.3x48= 13.2= 13.3= 14.1= 14.1x53= 14.2= 15.1

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
High
Integrity
High
Availability
High

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

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. Check Junos OS version
    Run 'show version' or 'show version detail' command on the device
    Affected if The installed version matches 12.3, 12.3X48, 13.2, 13.3, 14.1, 14.1X53, 14.2, or 15.1 (or any version between these that is not patched)
  2. Review system logs for commit failures
    Run 'show log messages' or 'show system commit' and search for 'statements constraint check failed' or commit failure events
    Affected if Recent commit attempts show 'statements constraint check failed' errors indicating a configuration triggered the vulnerability condition
  3. Check for unexpected console or mgmt access
    Run 'show system users' or review authentication logs for sessions that occurred without password prompt
    Affected if Users appear logged in via console, ssh, ftp, telnet, or su without corresponding successful authentication entries in the logs
  4. Verify commit history for failed configurations
    Run 'show system commit' and 'show system commit detail' to identify failed commit attempts and the associated configuration
    Affected if There are recent failed commits with partial configuration activation that could have left authentication in an unexpected state

The environment is affected if the Junos OS version is one of the affected versions listed AND there is evidence of a commit failure with 'statements constraint check failed' that may have resulted in unauthorized passwordless access.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS to the fixed versions (12.3R10+, 12.3X48-D20+, 13.2R8+, 13.3R7+, 14.1R4-S12+, 14.1X53-D30+, 14.2R4+, 15.1F2+/15.1F3+/15.1R2+) and review configurations for any that may cause commit failures.

Recommended fix High confidence

Upgrade to Junos 12.3R10/R11, 12.3X48-D20, 13.2R8, or 13.3R7 (or later stable releases in each respective branch)

  1. 1. Identify the current Junos OS version on the affected device using 'show version' command
  2. 2. Determine which branch (12.3, 12.3X48, 13.2, or 13.3) the device is running
  3. 3. Download the appropriate fixed Junos OS release from the Juniper Networks download portal
  4. 4. For 12.3 branch devices: upgrade to 12.3R10 or 12.3R11
  5. 5. For 12.3X48 branch devices: upgrade to 12.3X48-D20 or later
  6. 6. For 13.2 branch devices: upgrade to 13.2R8 or later
  7. 7. For 13.3 branch devices: upgrade to 13.3R7 or later
  8. 8. Upload the Junos upgrade package to the device using 'file copy' or USB
Caveat Standard Junos upgrade considerations apply - review release notes for compatibility, ensure configuration backup exists, and plan maintenance window as upgrade requires reboot

Generated from the published advisory — verify against the referenced sources before acting.

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-10601 — 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-10601 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