dbcve.org
Ata 190 FirmwareOperating system · Cisco

CVE-2022-20687

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
Multiple vulnerabilities in the Link Layer Discovery Protocol (LLDP) 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 the LLDP service to restart. These vulnerabilities are due to missing length validation of certain LLDP packet header fields. An attacker could exploit these vulnerabilities by sending a malicious LLDP packet to an affected device. A successful exploit could allow the attacker to execute code on the affected device and cause LLDP to restart unexpectedly, resulting in a denial of service (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

The vulnerability stems from missing length validation of specific LLDP (Link Layer Discovery Protocol) packet header fields in Cisco ATA 190 Series firmware. An unauthenticated remote attacker can send a maliciously crafted LLDP packet with malformed header fields to trigger the vulnerability. Successful exploitation allows arbitrary code execution on the device and causes the LLDP service to crash and restart, creating a denial of service condition.

MitigationApply the Cisco firmware update when available, or disable LLDP on the device if not required for operations. Additionally, restrict network access to the affected device to prevent unauthorized LLDP packets from reaching it.

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 use SNMP/cli to confirm the hardware is a Cisco ATA 190, ATA 191, or ATA 192 series analog telephone adapter
    Affected if Device model is ATA 190, ATA 191, or ATA 192
  2. Determine the firmware version
    Log into the device web interface and navigate to System > Software, or use the 'show version' command via CLI to obtain the current firmware build
    Affected if Firmware version is 'all versions' for ATA 190, or is lower than 11.2.2 / 12.0.1 for ATA 191, or lower than 11.2.2 for ATA 192
  3. Verify LLDP is enabled
    Access the device web interface under System > LLDP or use the CLI command 'show lldp' to check if Link Layer Discovery Protocol is turned on
    Affected if LLDP is enabled on the device (the vulnerability only triggers when LLDP is running)

User is affected if the device is an ATA 190/191/192 with LLDP enabled and running a firmware version within the affected ranges listed for that model

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 update when available, or disable LLDP on the device if not required for operations. Additionally, restrict network access to the affected device to prevent unauthorized LLDP packets from reaching it.

Recommended fix Moderate confidence

Cisco ATA 191: 12.0.2 or later (or 11.2.2); Cisco ATA 192: 11.2.2 or later; Cisco ATA 190: latest available firmware

  1. 1. Identify the current firmware version of the Cisco ATA device by accessing the web interface or using the administrative console.
  2. 2. For Cisco ATA 191 devices: Upgrade to firmware version 12.0.2 or later (or 11.2.2 if staying on the 11.x train).
  3. 3. For Cisco ATA 192 devices: Upgrade to firmware version 11.2.2 or later.
  4. 4. For Cisco ATA 190 devices: Upgrade to the latest available firmware version from Cisco's support portal.
  5. 5. After upgrade, verify the LLDP service is running properly and test LLDP functionality.
  6. 6. Consider disabling LLDP if not required in the network environment as an additional mitigation (via device web interface under Layer 2 settings).
Caveat Review Cisco release notes for the target firmware version for any configuration or feature changes before upgrading

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-20687 — 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-20687 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