# CVE-2022-20691: Denial of service in Cisco Analog Telephone Adaptor (ATA) Software

> An unauthenticated adjacent attacker can cause a denial of service on Cisco ATA devices by sending crafted CDP packets that exhaust memory.

- **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:** 3 Aug 2024
- **Also known as:** GHSA-3f75-4wmv-vpf2

## What is CVE-2022-20691?

CVE-2022-20691 is a medium-severity denial of service 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

A vulnerability in the Cisco Discovery Protocol functionality of Cisco ATA 190 Series Adaptive Telephone Adapter firmware could allow an unauthenticated, adjacent attacker to cause a DoS condition of an affected device.
 This vulnerability is due to missing length validation of certain Cisco Discovery Protocol packet header fields. 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 the device to exhaust available memory and cause the service to restart.
 Cisco has released firmware updates that address this vulnerability.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input), CWE-400 (Uncontrolled Resource Consumption)

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

It affects 3 products.


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

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

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

## Is CVE-2022-20691 being exploited?

There is no known exploitation of CVE-2022-20691 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-20691 and fix it if it is affected.

What it is: CVE-2022-20691 is a medium-severity denial of service 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-20691 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-20691/ (Markdown: https://insights.sbomify.com/CVE-2022-20691/index.md)
```

## Sources

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

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