VYPR
Unrated severityNVD Advisory· Published Sep 25, 2019· Updated Nov 20, 2024

Cisco IOS XE Software Consent Token Bypass Vulnerability

CVE-2019-12671

Description

Cisco IOS XE Software CLI vulnerability allows authenticated local attacker to bypass consent token and gain shell access to underlying OS.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Cisco IOS XE Software CLI vulnerability allows authenticated local attacker to bypass consent token and gain shell access to underlying OS.

Vulnerability

The vulnerability resides in the CLI of Cisco IOS XE Software. It stems from insufficient enforcement of the consent token when authorizing shell access. An authenticated local attacker can exploit this by requesting shell access. Affected versions include various Cisco IOS XE releases; consult the Cisco IOS Software Checker for specific affected releases [1].

Exploitation

An attacker must have authenticated access to the CLI of an affected device. The attacker then requests shell access, and due to the consent token bypass, the request is granted without proper authorization. No additional user interaction or network position is required beyond local CLI access [1].

Impact

Successful exploitation allows the attacker to gain shell access on the device and execute arbitrary commands on the underlying operating system. This results in full compromise of the device, including potential data exfiltration, further network attacks, and denial of service [1].

Mitigation

Cisco has released software updates to address this vulnerability. Customers should upgrade to a fixed release as identified by the Cisco IOS Software Checker. No workarounds are available. The vulnerability is not listed on the Known Exploited Vulnerabilities (KEV) catalog as of the publication date [1].

AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.