dbcve.org
Ios XrOperating system · Cisco

CVE-2017-6728

HIGH · 7.0 CVSS v3.0 Published 2017-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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 of Cisco IOS XR Software could allow an authenticated, local attacker to execute arbitrary code at the root privilege level on an affected system, because of Incorrect Permissions. More Information: CSCvb99389. Known Affected Releases: 6.2.1.BASE. Known Fixed Releases: 6.3.1.15i.BASE 6.2.3.1i.BASE 6.2.2.15i.BASE 6.1.4.10i.BASE.

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 local authenticated attacker with CLI access to Cisco IOS XR Software can execute arbitrary code at root privilege level due to incorrect permissions in the CLI. This is a local privilege escalation vulnerability requiring valid credentials.

MitigationApply the appropriate fixed release (6.3.1.15i.BASE, 6.2.3.1i.BASE, 6.2.2.15i.BASE, or 6.1.4.10i.BASE) or later. Follow Cisco IOS XR upgrade procedures and test thoroughly in a non-production environment before deployment.

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
Ios XrOperating system
Affected:all versions

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

CVSS:3.0/AV:L/AC:H/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. Check installed Cisco IOS XR version
    Access the device CLI and run 'show version' or 'show install active' to display the running IOS XR version
    Affected if The displayed version is earlier than 6.3.1.15i.BASE, 6.2.3.1i.BASE, 6.2.2.15i.BASE, or 6.1.4.10i.BASE (or any version prior to these fixed releases)
  2. Confirm CLI access is enabled
    Verify that the CLI interface is configured and accessible on the device using 'show running-config | include line' or by attempting to access the CLI prompt
    Affected if CLI access is available and the device runs a vulnerable IOS XR version
  3. Identify user privilege level
    After logging in with valid credentials, run 'show privilege' or 'who' to see your current privilege level
    Affected if You are logged in as an authenticated user with any privilege level on a vulnerable IOS XR version

You are affected if your Cisco IOS XR version is below the fixed releases (6.3.1.15i.BASE, 6.2.3.1i.BASE, 6.2.2.15i.BASE, or 6.1.4.10i.BASE) and CLI access with valid credentials is available on the device.

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 fixed release (6.3.1.15i.BASE, 6.2.3.1i.BASE, 6.2.2.15i.BASE, or 6.1.4.10i.BASE) or later. Follow Cisco IOS XR upgrade procedures and test thoroughly in a non-production environment before deployment.

Fix this in Ios Xr Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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