Ata 190 FirmwareOperating system · Cisco
CVE-2022-20691
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 Cisco Discovery Protocol functionality of Cisco ATA 190 Series Adaptive Telephone Adapter firmware could allow an unauthenticated, adjacent attacker to cause a DoS condition of an affected device. This vulnerability is due to missing length validation of certain Cisco Discovery Protocol packet header fields. An attacker could exploit this vulnerability by sending crafted Cisco Discovery Protocol packets to an affected device. A successful exploit could allow the attacker to cause the device to exhaust available memory and cause the service to restart. Cisco has released firmware updates that address this vulnerability.
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 confidenceA vulnerability in the Cisco Discovery Protocol of Cisco ATA 190 Series firmware lacks proper length validation of CDP packet header fields. An unauthenticated adjacent attacker can send crafted CDP packets to exhaust device memory, causing the service to restart and resulting in denial of service.
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
Ata 190 FirmwareOperating system
all versions
Ata 191 FirmwareOperating system
< 11.2.2< 12.0.1= 12.0.1
Ata 192 FirmwareOperating system
< 11.2.2CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device admin interface or check the physical device label to confirm it is a Cisco ATA 190, ATA 191, or ATA 192 series device.Affected if The device is not one of these three models, the device is not affected.
-
Check the installed firmware versionLog into the device web interface or use the command line interface (CLI) to retrieve the current firmware version. Typically found under Administration > System Information or via 'show version' command.Affected if Unable to determine the firmware version prevents assessment of vulnerability status.
-
Compare firmware version against affected rangesFor ATA 190: all versions are affected. For ATA 191: versions prior to 11.2.2, versions prior to 12.0.1, and exactly 12.0.1 are affected. For ATA 192: versions prior to 11.2.2 are affected. Versions 11.2.2 and above, and 12.0.1 and above for ATA 191 are NOT affected.Affected if The installed version falls within the affected ranges listed, indicating the device is vulnerable.
-
Verify if CDP is enabledCheck the device configuration for Cisco Discovery Protocol settings. In the web interface, look under Interface Settings or Network settings for CDP enable/disable status. Via CLI, use 'show cdp neighbor' or check the running configuration for 'cdp run'.Affected if CDP is enabled and the firmware version is in the affected range, the device is vulnerable to the denial of service condition.
The device is affected if it is a Cisco ATA 190, 191, or 192 with firmware version in the affected ranges and Cisco Discovery Protocol is enabled.
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 · scoped11.2.212.0.1
Apply the Cisco firmware update that addresses this vulnerability. As an interim control, restrict physical access to the network segment to limit adjacent attackers from reaching the CDP service.
Firmware version 11.2.2 or later for ATA 190/191/192 series
- Identify the current firmware version of the Cisco ATA 190 Series device by accessing the device's web interface or using the appropriate show command
- Download the fixed firmware version 11.2.2 or later from Cisco's official software download center (sec.cloudapps.cisco.com)
- Access the device's web-based management interface using an administrative account
- Navigate to the firmware upgrade section (typically under Administration > System Management > Software Update)
- Upload and apply the new firmware file to the device
- Allow the device to complete the firmware upgrade process and automatically reboot
- After the device restarts, verify the new firmware version is installed and the device is functioning normally
- Confirm the Cisco Discovery Protocol service is operational
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ata 190 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20691 — 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-20691 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