dbcve.org
JunosOperating system · Juniper

CVE-2017-10602

HIGH · 7.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 →
80/100
Remediation priority · High
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 buffer overflow vulnerability in Junos OS CLI may allow a local authenticated user with read only privileges and access to Junos CLI, to execute code with root privileges. Affected releases are Juniper Networks Junos OS: 14.1X53 versions prior to 14.1X53-D46 on EX2200/VC, EX3200, EX3300/VC, EX4200, EX4300, EX4550/VC, EX4600, EX6200, EX8200/VC (XRE), QFX3500, QFX3600, QFX5100; 14.1X53 versions prior to 14.1X53-D130 on QFabric System; 14.2 versions prior to 14.2R4-S9, 14.2R6; 15.1 versions prior to 15.1F5, 15.1R3; 15.1X49 versions prior to 15.1X49-D40 on SRX Series; 15.1X53 versions prior to 15.1X53-D47 on NFX150, NFX250; 15.1X53 versions prior to 15.1X53-D65 on QFX10000 Series; 15.1X53 versions prior to 15.1X53-D233 on QFX5110, QFX5200.

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 buffer overflow in Junos OS CLI allows a local authenticated user with read-only privileges to execute arbitrary code with root privileges. The vulnerability exists in the CLI parsing mechanism and can be exploited by providing specially crafted input that overflows a buffer, enabling privilege escalation from read-only user to root.

MitigationApply the appropriate Junos OS software update as specified in the Juniper advisory (14.1X53-D46/D130, 14.2R4-S9/14.2R6, 15.1F5/15.1R3, 15.1X49-D40, 15.1X53-D47/D65/D233 depending on platform). Prior to deployment, validate the current Junos version and schedule a maintenance window with validated backups and rollback procedures.

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:= 14.1x53= 14.2= 15.1= 15.1x49= 15.1x49-d10= 15.1x49-d20= 15.1x49-d30= 15.1x49-d35= 15.1x53

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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. Determine installed Junos OS version
    Execute 'show version' or 'request system version' command in the CLI to retrieve the running Junos version
    Affected if The displayed version matches or falls within any of the affected releases: 14.1x53, 14.2, 15.1, 15.1x49 (including d10/d20/d30/d35 variants), or 15.1x53
  2. Confirm CLI access for read-only users
    Review user account configuration via 'show configuration system login' to identify accounts with 'class read-only' or similar restricted privilege levels
    Affected if Any local or authenticated remote users exist with read-only class privileges, enabling them to access the CLI
  3. Verify local authentication is enabled
    Check authentication settings via 'show configuration system authentication-order' and confirm local accounts are permitted
    Affected if Local authentication or RADIUS/TACACS+ with read-only user accounts is configured, allowing authenticated access to the CLI

The system is affected if it runs any Junos version in the 14.1x53, 14.2, 15.1, 15.1x49, or 15.1x53 families AND allows authenticated read-only users to access the CLI, as the buffer overflow can be triggered by such users to escalate to root privileges.

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

Apply the appropriate Junos OS software update as specified in the Juniper advisory (14.1X53-D46/D130, 14.2R4-S9/14.2R6, 15.1F5/15.1R3, 15.1X49-D40, 15.1X53-D47/D65/D233 depending on platform). Prior to deployment, validate the current Junos version and schedule a maintenance window with validated backups and rollback procedures.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-10602 — 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-10602 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