dbcve.org
Ios XeOperating system · Cisco

CVE-2022-20919

HIGH · 7.5 CVSS v3.1 Published 2022-09-30
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
Remotely reachable No privileges 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 processing of malformed Common Industrial Protocol (CIP) packets that are sent to Cisco IOS Software and Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause an affected device to unexpectedly reload, resulting in a denial of service (DoS) condition. This vulnerability is due to insufficient input validation during processing of CIP packets. An attacker could exploit this vulnerability by sending a malformed CIP packet to an affected device. A successful exploit could allow the attacker to cause the affected device to unexpectedly reload, resulting in a DoS condition.

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 denial of service vulnerability exists in Cisco IOS and IOS XE software where malformed Common Industrial Protocol (CIP) packets with insufficient input validation cause affected devices to unexpectedly reload. An unauthenticated remote attacker can trigger this by sending specially crafted CIP packets to the target device.

MitigationApply the appropriate Cisco software update (patch) for IOS/IOS XE when available. Implement network segmentation and access controls to limit exposure of affected devices to untrusted networks until the patch can be 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
Ios XeOperating system
Affected:= 17.9.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device is running Cisco IOS XE
    Log into the device and run 'show version' or check the device型号 and software type to confirm it runs Cisco IOS XE software rather than classic IOS
    Affected if The device does not run Cisco IOS XE software - this vulnerability only affects IOS XE
  2. Check the installed IOS XE version
    Run 'show version' and locate the IOS XE version number in the output (typically displayed as something like 17.9.1 or 17.9.x)
    Affected if The installed version is 17.9.1 exactly - this is the specific version listed as affected
  3. Determine if CIP protocol is enabled or configured
    Check the device configuration for any CIP-related settings using 'show running-config | include cip' or review industrial automation protocol configurations if applicable
    Affected if CIP (Common Industrial Protocol) is enabled or configured on the device - the vulnerability is triggered specifically by malformed CIP packets being sent to the device
  4. Verify the device is exposed to untrusted network traffic
    Review network access controls and firewall rules to determine if the device can receive CIP packets from untrusted or external network sources
    Affected if The device can receive CIP packets from unauthenticated remote attackers on the network - this is required for exploitation

A user is affected if they run Cisco IOS XE version 17.9.1, have CIP protocol enabled, and the device is reachable by untrusted network sources that could send malformed CIP packets.

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 Cisco software update (patch) for IOS/IOS XE when available. Implement network segmentation and access controls to limit exposure of affected devices to untrusted networks until the patch can be applied.

Fix this in Ios Xe Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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