dbcve.org
Ata 190 FirmwareOperating system · Cisco

CVE-2022-20688

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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 Cisco Discovery Protocol functionality of Cisco ATA 190 Series Analog Telephone Adapter firmware could allow an unauthenticated, remote attacker to execute arbitrary code on an affected device and cause Cisco Discovery Protocol service to restart. This vulnerability is due to missing length validation of certain Cisco Discovery Protocol packet header fields. 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 execute code on the affected device and cause Cisco Discovery Protocol to restart unexpectedly, 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 · moderate confidence

A buffer overflow vulnerability in Cisco ATA 190 Series Analog Telephone Adapters exists due to missing length validation of Cisco Discovery Protocol packet header fields. An unauthenticated remote attacker can send a malicious CDP packet to execute arbitrary code on the affected device and cause a denial of service by restarting the CDP service.

MitigationApply the vendor firmware patch when available; until then, consider filtering Cisco Discovery Protocol traffic at network boundaries to block external CDP packets.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 model
    Access the device web interface or check the physical device label to confirm the model is Cisco ATA 190, ATA 191, or ATA 192 series
    Affected if Device model is ATA 190 (all versions), ATA 191 (< 11.2.2, < 12.0.1, or 12.0.1), or ATA 192 (< 11.2.2)
  2. Check the firmware version
    Log into the device web interface and navigate to System Setup > Software Upgrade, or use the command-line interface and run 'show version' to determine the installed firmware version
    Affected if Firmware version falls within the affected ranges listed for your model
  3. Verify if Cisco Discovery Protocol is enabled
    Access the device web interface, go to Advanced Settings > Cisco Discovery Protocol (CDP), or use the CLI and run 'show cdp' to check if CDP is enabled
    Affected if CDP is enabled on the device (this is the attack surface for the vulnerability)
  4. Confirm network accessibility
    Verify that the device is reachable on the network where it could receive CDP packets from untrusted sources
    Affected if The device is directly accessible on a network segment where untrusted devices can send CDP packets

You are affected if you have a vulnerable ATA 190/191/192 model running a firmware version within the affected ranges AND CDP is enabled, allowing external CDP packets to reach the device.

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 vendor firmware patch when available; until then, consider filtering Cisco Discovery Protocol traffic at network boundaries to block external CDP packets.

Recommended fix Moderate confidence

Firmware version 11.2.2 or later for ATA 190/191/192 series

  1. 1. Identify the specific ATA model (190, 191, or 192) in use
  2. 2. Access the device administration interface or use the device's web-based utility
  3. 3. Navigate to the firmware upgrade or administration section
  4. 4. Download the appropriate firmware version from the Cisco website: version 11.2.2 or later for ATA 191 and ATA 192; version 11.2.2 or later for ATA 190
  5. 5. Upload and apply the firmware upgrade to the device
  6. 6. After upgrade, verify the Cisco Discovery Protocol service is running normally
  7. 7. Confirm the device is no longer vulnerable by checking the running firmware version
Caveat Standard firmware upgrade - review Cisco release notes for any configuration changes required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ata 190 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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