Ata 190 FirmwareOperating system · Cisco
CVE-2022-20686
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 · uneditedMultiple 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 confidenceMissing length validation in LLDP packet header fields allows malformed packets to trigger buffer overflows, enabling unauthenticated remote attackers to execute arbitrary code on affected Cisco ATA 190 devices and cause the LLDP service to crash.
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
all versions
Ata 191 FirmwareOperating system
< 11.2.2< 12.0.1= 12.0.1
Ata 192 FirmwareOperating system
< 11.2.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelDetermine if the device is a Cisco ATA 190, ATA 191, or ATA 192 series analog telephone adapter. This can be done via the device web interface, physical label, or CLI command such as 'show version' or checking the device inventory.Affected if The device is not a Cisco ATA 190, 191, or 192 model - otherwise continue to next step
-
Check firmware versionRetrieve the current firmware version from the device. On Cisco ATA devices, this is typically shown in the web interface under Administration > System > Software or via CLI command 'show version' or 'show firmware'.Affected if For ATA 190: any version (all versions affected). For ATA 191: version is less than 11.2.2, OR less than 12.0.1, OR equals 12.0.1. For ATA 192: version is less than 11.2.2 - if any of these conditions are true, the device is running a vulnerable version
-
Verify LLDP statusCheck whether Link Layer Discovery Protocol (LLDP) is enabled on the device. This can be verified via the web interface under Network Settings or Port Configuration, or via CLI command such as 'show lldp' or 'show run lldp'.Affected if LLDP is enabled - the device is actively processing LLDP packets and is vulnerable to the buffer overflow when malformed packets are received
If the device is a Cisco ATA 190, 191, or 192 running a firmware version within the affected ranges AND LLDP is enabled, the environment is vulnerable to remote code execution or service crash via malformed LLDP packets.
Generated from the published advisory. Verify against your own configuration.
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 · scoped11.2.212.0.1
Apply Cisco firmware updates when available; alternatively, disable LLDP on the device or restrict network access to prevent untrusted LLDP packets from reaching the device.
ATA 191: 11.2.2 or later / 12.0.2 or later; ATA 192: 11.2.2 or later / 12.0.2 or later; ATA 190: latest available version
- 1. Identify the exact model number (ATA 190, ATA 191, or ATA 192) of the affected device
- 2. Determine the current firmware version by accessing the device's web interface or using the show version command via CLI
- 3. For ATA 191 devices: upgrade to firmware version 11.2.2 or later, or 12.0.2 or later
- 4. For ATA 192 devices: upgrade to firmware version 11.2.2 or later, or 12.0.2 or later
- 5. For ATA 190 devices: upgrade to the latest available firmware version from Cisco
- 6. Download the firmware from the Cisco Software Download center (requires valid Cisco service contract)
- 7. Access the device web interface, navigate to Administration > Firmware Upgrade, and upload the new firmware file
- 8. Allow the device to reboot and verify the upgrade was successful
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 / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20686 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-20686 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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