iOSOperating system · Cisco

CVE-2019-12670

MEDIUM · 6.7 CVSS v3.1 Published 2019-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 filesystem of Cisco IOS XE Software could allow an authenticated, local attacker within the IOx Guest Shell to modify the namespace container protections on an affected device. The vulnerability is due to insufficient file permissions. An attacker could exploit this vulnerability by modifying files that they should not have access to. A successful exploit could allow the attacker to remove container protections and perform file actions outside the namespace of the container.

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

This is a local container escape vulnerability in Cisco IOS XE Software where the IOx Guest Shell container has insufficient file permissions. An authenticated attacker within the IOx Guest Shell can modify files to remove container namespace protections, allowing them to perform file operations outside the container's isolated namespace.

MitigationApply the Cisco IOS XE software update that patches the file permission vulnerability in the IOx Guest Shell filesystem. Restrict access to the IOx Guest Shell to trusted, privileged users until the patch is applied.

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
iOSOperating system
Affected:= 16.10.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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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. Verify IOx Guest Shell is enabled
    Execute 'show iox' or 'show guestshell' from the IOS XE CLI to confirm IOx/Guest Shell feature is active on the device
    Affected if IOx Guest Shell is running or deployed on the device
  2. Confirm the IOS XE version
    Run 'show version' to display the installed Cisco IOS XE software version and compare it to 16.10.1
    Affected if The installed version equals exactly 16.10.1
  3. Check Guest Shell filesystem permissions
    From within the Guest Shell container, run 'ls -la /' and inspect file permissions. Specifically look at critical system directories and files for world-writable permissions or missing immutable flags
    Affected if Any system files or directories in the Guest Shell have overly permissive permissions (such as world-writable) that would allow modification to escape namespace isolation
  4. Test namespace isolation boundary
    From inside the Guest Shell, attempt to access device filesystem paths outside the container namespace (such as checking if paths like /tftpboot or /bootflash are accessible when they should be isolated)
    Affected if Files or directories outside the container's isolated namespace are readable or writable from within the Guest Shell

A device is affected if it runs Cisco IOS XE version 16.10.1, has IOx Guest Shell enabled, and the Guest Shell filesystem allows access to files outside its isolated container namespace.

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 Cisco IOS XE software update that patches the file permission vulnerability in the IOx Guest Shell filesystem. Restrict access to the IOx Guest Shell to trusted, privileged users until the patch is applied.

Fix this in iOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2019-12670 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