dbcve.org
Ata 190 FirmwareOperating system · Cisco

CVE-2022-20690

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 the Cisco Discovery Protocol (CDP) parsing code of Cisco ATA 190 Series Analog Telephone Adapters. Missing length validation checks allow an unauthenticated adjacent attacker to send malformed CDP packets that trigger out-of-bounds memory reads, leading to corruption of the internal CDP database.

MitigationApply the Cisco firmware patch when available; as a workaround, consider disabling CDP on vulnerable interfaces if the device supports this configuration.

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 ATA device model
    Access the device web interface or CLI and locate the hardware model number (ATA 190, ATA 191, or ATA 192) in the device status or system information page
    Affected if Model is Cisco ATA 190, ATA 191, or ATA 192
  2. Determine the installed firmware version
    In the device web interface, go to System > Software or use the CLI command 'show version' to retrieve the firmware version number
    Affected if Version is less than 11.2.2 for ATA 191/192, or any version for ATA 190 (including versions 11.2.2, 12.0.1 for ATA 191)
  3. Verify CDP is enabled on the device
    Access the device CLI and run 'show cdp' or check the web interface under the relevant interface settings to see if Cisco Discovery Protocol is actively running
    Affected if CDP is enabled and processing packets on any interface
  4. Assess network accessibility of CDP service
    From a system on the same network segment, use a packet capture tool or CDP-aware discovery tool to verify CDP packets can reach the device interface
    Affected if The device is reachable by an unauthenticated adjacent attacker on the same broadcast domain and CDP is running

The device is affected if it is an ATA 190 (any firmware), an ATA 191 running firmware below 12.0.2 or version 12.0.1, or an ATA 192 running firmware below 11.2.2, AND CDP is enabled and accessible from the adjacent network segment.

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 workaround, consider disabling CDP on vulnerable interfaces if the device supports this configuration.

Recommended fix Moderate confidence

ATA 191/192: upgrade to firmware 11.2.2 or later; ATA 190: contact Cisco for support

  1. 1. Identify the specific ATA 190 series model (ATA 190, ATA 191, or ATA 192) from the device label or web interface.
  2. 2. Access the device web interface by navigating to the device IP address.
  3. 3. Navigate to Administration > System Software > Software Upgrade or similar path depending on firmware version.
  4. 4. Download the appropriate firmware from Cisco's software download center (software.cisco.com) - search for Cisco ATA 190 Series Analog Telephone Adapter.
  5. 5. Upload the firmware file (11.2.2 or later for ATA 191/192) to the device and initiate the upgrade.
  6. 6. Wait for the upgrade to complete and the device to reboot automatically.
  7. 7. Verify the new firmware version in the device web interface under Administration > Device Information.
Caveat Standard firmware upgrade - ensure power continuity; backup configuration if possible

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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