# CVE-2022-20689: Memory corruption in Cisco Analog Telephone Adaptor (ATA) Software

> An unauthenticated adjacent attacker can cause memory corruption and potential information disclosure on Cisco ATA devices by sending malicious CDP packets.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Dec 2022
- **Updated:** 1 Nov 2024
- **Also known as:** GHSA-8pwq-5wx2-r2fc

## What is CVE-2022-20689?

CVE-2022-20689 is a medium-severity memory corruption vulnerability in Cisco Analog Telephone Adaptor (ATA) Software, published on 7 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input), CWE-130 (Improper Handling of Length Parameter Inconsistency)

## Which versions are affected by CVE-2022-20689?

It affects 3 products.


Products: Cisco Ata 190 Firmware, Cisco Ata 191 Firmware, Cisco Ata 192 Firmware.

## How do I fix CVE-2022-20689?

No fix has been published for CVE-2022-20689 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-20689 being exploited?

There is no known exploitation of CVE-2022-20689 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Analog Telephone Adaptor (ATA) Software

- [CVE-2021-34710](https://insights.sbomify.com/CVE-2021-34710/): Cisco ATA 190 Series Analog Telephone Adapter Software Vulnerabilities (high 8.8)
- [CVE-2021-34735](https://insights.sbomify.com/CVE-2021-34735/): Cisco ATA 190 Series Analog Telephone Adapter Software Vulnerabilities (high 8.8)
- [CVE-2022-20686](https://insights.sbomify.com/CVE-2022-20686/): Memory corruption in Cisco Analog Telephone Adaptor (ATA) Software (medium 5.3)
- [CVE-2022-20687](https://insights.sbomify.com/CVE-2022-20687/): Memory corruption in Cisco Analog Telephone Adaptor (ATA) Software (medium 5.3)
- [CVE-2022-20688](https://insights.sbomify.com/CVE-2022-20688/): Memory corruption in Cisco Analog Telephone Adaptor (ATA) Software (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-20689 and fix it if it is affected.

What it is: CVE-2022-20689 is a medium-severity memory corruption vulnerability in Cisco Analog Telephone Adaptor (ATA) Software, published on 7 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-20689 in the wild and no public exploit code.

Affected product: Cisco Analog Telephone Adaptor (ATA) Software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-20689/ (Markdown: https://insights.sbomify.com/CVE-2022-20689/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-20689
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-20689
- OSV: https://osv.dev/vulnerability/CVE-2022-20689

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-20689/
Summaries are generated and may contain mistakes; the official description above is the record.