dbcve.org
StarosOperating system · Cisco

CVE-2017-6707

HIGH · 8.2 CVSS v3.0 Published 2017-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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 vulnerability in the CLI command-parsing code of the Cisco StarOS operating system for Cisco ASR 5000 Series 11.0 through 21.0, 5500 Series, and 5700 Series devices and Cisco Virtualized Packet Core (VPC) Software could allow an authenticated, local attacker to break from the StarOS CLI of an affected system and execute arbitrary shell commands as a Linux root user on the system, aka Command Injection. The vulnerability exists because the affected operating system does not sufficiently sanitize commands before inserting them into Linux shell commands. An attacker could exploit this vulnerability by submitting a crafted CLI command for execution in a Linux shell command as a root user. Cisco Bug IDs: CSCvc69329, CSCvc72930.

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

Command injection vulnerability in Cisco StarOS CLI command-parsing allows authenticated local attackers to escape the StarOS CLI and execute arbitrary Linux shell commands as root. The flaw exists because the OS insufficiently sanitizes commands before passing them to Linux shell commands.

MitigationApply the relevant Cisco patch or upgrade StarOS to a version beyond 21.0 as specified in Cisco Bug IDs CSCvc69329 and CSCvc72930. Restrict CLI access to trusted, authorized personnel only.

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
StarosOperating system
Affected:= 11.0_base= 12.0.0= 12.1_base= 12.2\(300\)= 12.2_base= 14.0\(600\)= 14.0.0= 15.0\(912\)= 15.0\(935\)= 15.0\(938\)= 15.0_base= 16.0\(900\)

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/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. Identify the product and operating system
    Run the command 'show version' or check the system boot image to confirm the device is running Cisco StarOS
    Affected if The system is running Cisco StarOS and the version matches one of the affected versions listed (11.0_base, 12.0.0, 12.1_base, 12.2(300), 12.2_base, 14.0(600), 14.0.0, 15.0(912), 15.0(935), 15.0(938), 15.0_base, or 16.0(900))
  2. Verify the installed StarOS version
    Use the 'show version' command in the StarOS CLI to retrieve the exact version number and compare it against the affected version list
    Affected if The displayed version matches any of the affected versions: 11.0_base, 12.0.0, 12.1_base, 12.2(300), 12.2_base, 14.0(600), 14.0.0, 15.0(912), 15.0(935), 15.0(938), 15.0_base, or 16.0(900)
  3. Confirm CLI access is configured
    Check if the StarOS CLI is accessible by verifying that local or remote CLI authentication is enabled and that user accounts exist with CLI login privileges
    Affected if CLI access is enabled and users have authenticated access to the StarOS CLI (the vulnerability requires authenticated local attacker access)

You are affected if your device runs Cisco StarOS version 11.0_base, 12.0.0, 12.1_base, 12.2(300), 12.2_base, 14.0(600), 14.0.0, 15.0(912), 15.0(935), 15.0(938), 15.0_base, or 16.0(900) and has CLI access enabled for authenticated users.

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 relevant Cisco patch or upgrade StarOS to a version beyond 21.0 as specified in Cisco Bug IDs CSCvc69329 and CSCvc72930. Restrict CLI access to trusted, authorized personnel only.

Fix this in Staros Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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