dbcve.org
Ata 190 FirmwareOperating system · Cisco

CVE-2022-20689

HIGH · 8.8 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to 11.2.2 / 12.0.1 or later.
See remediation →
93/100
Remediation priority · Urgent
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
Multiple vulnerabilities in the Cisco Discovery Protocol functionality of Cisco ATA 190 Series Analog Telephone Adapter firmware could allow an unauthenticated, adjacent attacker to cause Cisco Discovery Protocol memory corruption on an affected device. These vulnerabilities are due to missing length validation checks when processing Cisco Discovery Protocol messages. An attacker could exploit these vulnerabilities by sending a malicious Cisco Discovery Protocol packet to an affected device. A successful exploit could allow the attacker to cause an out-of-bounds read of the valid Cisco Discovery Protocol packet data, which could allow the attacker to cause corruption in the internal Cisco Discovery Protocol database of 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 confidence

The vulnerability exists in Cisco Discovery Protocol (CDP) parsing within Cisco ATA 190 Series Analog Telephone Adapter firmware. Missing length validation checks allow a malformed CDP packet to trigger an out-of-bounds read, leading to memory corruption in the internal CDP database. An unauthenticated attacker on the adjacent network can exploit this by sending a specifically crafted CDP packet.

MitigationApply the Cisco firmware patch when available. As a compensating control, disable Cisco Discovery Protocol on the device if the feature is not required, or implement network segmentation to restrict adjacent network access.

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
Affected:all versions
Ata 191 FirmwareOperating system
Affected:< 11.2.2< 12.0.1= 12.0.1
Ata 192 FirmwareOperating system
Affected:< 11.2.2

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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. Identify the Cisco ATA device model
    Access the device web interface or CLI and retrieve the hardware model information. Look for ATA 190, ATA 191, or ATA 192 in the device status or system information page.
    Affected if The device is a Cisco ATA 190, ATA 191, or ATA 192 series analog telephone adapter.
  2. Check the installed firmware version
    Access the device web interface under System Information or use the CLI command 'show version' to retrieve the firmware version number.
    Affected if The firmware version is: ATA 190 (all versions), ATA 191 (any version before 11.2.2, before 12.0.1, or exactly 12.0.1), or ATA 192 (any version before 11.2.2).
  3. Verify if Cisco Discovery Protocol is enabled
    Access the device CLI and run 'show cdp neighbors' or check the web interface configuration for CDP settings. If CDP is disabled, the parsing code path may not be reachable.
    Affected if CDP is enabled on the device (the vulnerability触发 in the CDP parsing code when a malformed packet is received).
  4. Assess network accessibility to CDP
    Determine if the device is directly accessible from an adjacent network segment. Check if untrusted network segments can send CDP packets to the device interface.
    Affected if The device is reachable from an adjacent network where an unauthenticated attacker could send CDP packets to the device.

If the device is a Cisco ATA 190/191/192 with an affected firmware version and CDP is enabled, the device is vulnerable to CVE-2022-20689 when reachable by an adjacent network attacker.

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.

dbcve · scoped
Upgrade available Upgrade to 11.2.2 / 12.0.1 or later
Fixed in 11.2.212.0.1
Interim mitigation

Apply the Cisco firmware patch when available. As a compensating control, disable Cisco Discovery Protocol on the device if the feature is not required, or implement network segmentation to restrict adjacent network access.

Recommended fix High confidence

ATA 191/192: Upgrade to firmware version 12.0.1 or later; ATA 190: Contact Cisco for fixed firmware

  1. 1. Identify the specific ATA model (190, 191, or 192) in your environment
  2. 2. Access the device administration interface or use TFTP for firmware updates
  3. 3. Obtain the appropriate firmware version: For ATA 191 and 192, upgrade to version 12.0.1 or later; for ATA 190 (all versions), contact Cisco for remediation guidance
  4. 4. Verify the current firmware version by accessing the device web interface or via SIP OPTIONS request
  5. 5. Apply the firmware upgrade following Cisco's standard ATA firmware update procedure
  6. 6. After upgrade, verify the new firmware version is installed and the device is functioning properly
  7. 7. Consider disabling Cisco Discovery Protocol (CDP) on adjacent network segments if upgrade is not immediately possible as a temporary mitigation
Caveat Review Cisco ATA 190 release notes for any feature changes or configuration requirements between your current version and 12.0.1

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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