# CVE-2024-20463: Cisco ATA 190 Series Analog Telephone Adapter Firmware Command Injection and Denial of Service Vulnerability

> Unauthenticated remote attackers can modify configuration or reboot Cisco ATA 190 devices via GET requests, causing denial of service.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Oct 2024
- **Updated:** 31 Oct 2024
- **Also known as:** GHSA-8vcm-p6g6-xjqp

## What is CVE-2024-20463?

CVE-2024-20463 is a medium-severity missing authorization vulnerability in Cisco Analog Telephone Adaptor (ATA) Software, published on 16 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web-based management interface of Cisco ATA 190 Series Analog Telephone Adapter firmware could allow an unauthenticated, remote attacker to modify the configuration or reboot an affected device.

This vulnerability is due to the HTTP server allowing state changes in GET requests. An attacker could exploit this vulnerability by sending a malicious request to the web-based management interface on an affected device. A successful exploit could allow the attacker to make limited modifications to the configuration or reboot the device, resulting in a denial of service (DoS) condition. 

Weakness: CWE-862 (Missing Authorization), CWE-305 (Authentication Bypass by Primary Weakness)

## Which versions are affected by CVE-2024-20463?

It affects 2 products.


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

## How do I fix CVE-2024-20463?

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

## Is CVE-2024-20463 being exploited?

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

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

- [CVE-2024-20458](https://insights.sbomify.com/CVE-2024-20458/): Cisco ATA 190 Series Analog Telephone Adapter Software Vulnerabilities (high 8.2)
- [CVE-2024-20421](https://insights.sbomify.com/CVE-2024-20421/): Cisco ATA 190 Series Analog Telephone Adapter Firmware Cross-Site Request Forgery Vulnerability (high 7.1)
- [CVE-2024-20459](https://insights.sbomify.com/CVE-2024-20459/): Cisco ATA 190 Series Analog Telephone Adapter Muliplatform Firmware Command Injection Vulnerability (medium 6.5)
- [CVE-2024-20460](https://insights.sbomify.com/CVE-2024-20460/): Cisco ATA 190 Series Analog Telephone Adapter Firmware Reflected Cross-Site Scripting Vulnerability (medium 6.1)
- [CVE-2024-20461](https://insights.sbomify.com/CVE-2024-20461/): Cisco ATA 190 Series Analog Telephone Adapter Firmware Command Injection Vulnerability (medium 6.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20463 and fix it if it is affected.

What it is: CVE-2024-20463 is a medium-severity missing authorization vulnerability in Cisco Analog Telephone Adaptor (ATA) Software, published on 16 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-20463 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-2024-20463/ (Markdown: https://insights.sbomify.com/CVE-2024-20463/index.md)
```

## Sources

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

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