dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2022-20766

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Adaptive Telephone Adapter firmware could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to an out-of-bounds read when processing Cisco Discovery Protocol packets. 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 a service restart.Cisco has released firmware updates that address this vulnerability. There are no workarounds 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 confidence

An out-of-bounds read vulnerability exists in the Cisco Discovery Protocol packet processing of Cisco ATA 190 Series Adaptive Telephone Adapter firmware. An unauthenticated remote attacker can send crafted CDP packets to trigger the vulnerability, causing a service restart and resulting in denial of service.

MitigationApply the Cisco firmware update for the ATA 190 Series. No workarounds are available; the device must be updated to a patched firmware version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Confirm device model
    Identify the Cisco ATA 190 Series Adaptive Telephone Adapter by checking the device label, web interface, or administrative console for the model number
    Affected if The device is not a Cisco ATA 190 Series adapter
  2. Identify firmware version
    Access the device's web interface or administrative console and navigate to the firmware/version information section. Note the exact firmware version number installed
    Affected if The firmware version has not been updated to include the CVE-2022-20766 patch
  3. Check CDP service status
    Examine the device configuration to determine if Cisco Discovery Protocol (CDP) is enabled. Look for CDP-related settings in the network or interface configuration area of the device administration panel
    Affected if CDP is enabled and processing packets on the device interfaces
  4. Monitor for service disruption
    Review system logs or status indicators for repeated service restarts, crashes, or unexpected denial of service events that could indicate exploitation
    Affected if The device exhibits unexplained service restarts or denial of service conditions

You are affected if you have a Cisco ATA 190 Series device with an unpatched firmware version and Cisco Discovery Protocol is enabled, allowing unauthenticated remote attackers to trigger the out-of-bounds read via crafted CDP 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco firmware update for the ATA 190 Series. No workarounds are available; the device must be updated to a patched firmware version.

Recommended fix Moderate confidence

Latest available firmware for Cisco ATA 190 Series (contact Cisco for specific version numbers)

  1. Locate the Cisco ATA 190 Series Adaptive Telephone Adapter in your environment
  2. Navigate to the Cisco software download page for ATA 190 Series
  3. Download the latest available firmware version for your specific ATA 190 model
  4. Follow Cisco's firmware upgrade instructions for the ATA 190 Series to apply the update
  5. Verify the device is functioning normally after the upgrade
Caveat Review Cisco release notes for any configuration or compatibility considerations before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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