CVE-2022-20851
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 · uneditedA vulnerability in the web UI feature of Cisco IOS XE Software could allow an authenticated, remote attacker to perform an injection attack against an affected device. This vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by sending crafted input to the web UI API. A successful exploit could allow the attacker to execute arbitrary commands on the underlying operating system with root privileges. To exploit this vulnerability, an attacker must have valid Administrator privileges on the affected device.
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 confidenceAuthenticated command injection vulnerability in Cisco IOS XE web UI API. An attacker with valid Administrator credentials can send crafted input to the web UI API that is not properly validated, allowing execution of arbitrary commands on the underlying OS with root privileges.
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= 17.6.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the IOS XE versionRun 'show version' or 'show version | include Version' to display the running Cisco IOS XE versionAffected if The displayed version is exactly 17.6.1 (this specific version is affected)
-
Confirm the product is IOS XERun 'show version' and verify the output indicates Cisco IOS XE (not classic IOS or other platforms)Affected if The device runs Cisco IOS XE version 17.6.1 specifically
-
Check if the web UI is enabledRun 'show ip http server status' or 'show running-config | include ip http' to see if the HTTP/HTTPS web UI server is activeAffected if HTTP or HTTPS server is enabled (the vulnerability requires the web UI API to be accessible)
-
Verify web UI management accessCheck ACLs or interface configurations for HTTP/HTTPS services using 'show running-config | include http' or review interface IP assignments where web UI is boundAffected if The web UI is exposed to untrusted networks or accessible from management interfaces without ACL protection
The environment is affected if the device runs Cisco IOS XE version 17.6.1 AND the web UI (HTTP/HTTPS) feature is enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedApply Cisco's official patch for this vulnerability. Until then, disable the web UI feature if not required, restrict access via ACLs to trusted management networks only, and ensure strong Administrator credentials.
Cisco IOS XE 17.6.2 or later fixed release in the 17.6.x train
- 1. Identify the current Cisco IOS XE version running on the affected device using 'show version' command
- 2. If the device is running version 17.6.1, plan for an upgrade to a fixed release
- 3. Download the fixed Cisco IOS XE software image from Cisco's software download center (software.cisco.com)
- 4. Verify the image integrity using the MD5/SHA256 hash provided by Cisco
- 5. Upload the new IOS XE image to the device using TFTP, FTP, or SCP
- 6. Set the boot variable to point to the new image using 'boot system' command
- 7. Reload the device to apply the new IOS XE version
- 8. After reboot, verify the new version is running using 'show version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20851 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-20851 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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