# CVE-2024-20357: Memory corruption in Cisco IP Phones with Multiplatform Firmware

> Unauthenticated remote attackers can initiate calls or play sounds on Cisco IP phones due to missing bounds checking in XML parsing.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-49gp-r5pw-pqg8

## What is CVE-2024-20357?

CVE-2024-20357 is a medium-severity memory corruption vulnerability in Cisco IP Phones with Multiplatform Firmware, published on 1 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the XML service of Cisco IP Phone firmware could allow an unauthenticated, remote attacker to initiate phone calls on an affected device.  

 This vulnerability exists because bounds-checking does not occur while parsing XML requests. An attacker could exploit this vulnerability by sending a crafted XML request to an affected device. A successful exploit could allow the attacker to initiate calls or play sounds on the device.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 18 products.


Products: Cisco Ip Phone 6821 With Multiplatform Firmware, Cisco Ip Phone 6841 With Multiplatform Firmware, Cisco Ip Phone 6851 With Multiplatform Firmware, Cisco Ip Phone 6861 With Multiplatform Firmware, Cisco Ip Phone 6871 With Multiplatform Firmware, Cisco Ip Phone 7811 With Multiplatform Firmware, Cisco Ip Phone 7821 With Multiplatform Firmware, Cisco Ip Phone 7832 With Multiplatform Firmware, Cisco Ip Phone 7841 With Multiplatform Firmware, Cisco Ip Phone 7861 With Multiplatform Firmware, Cisco Ip Phone 8811 With Multiplatform Firmware, Cisco Ip Phone 8832 With Multiplatform Firmware, Cisco Ip Phone 8841 With Multiplatform Firmware, Cisco Ip Phone 8845 With Multiplatform Firmware, Cisco Ip Phone 8851 With Multiplatform Firmware, Cisco Ip Phone 8861 With Multiplatform Firmware, Cisco Ip Phone 8865 With Multiplatform Firmware, Cisco Video Phone 8875 Firmware.

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

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

## Is CVE-2024-20357 being exploited?

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

## Other vulnerabilities in Cisco IP Phones with Multiplatform Firmware

- [CVE-2024-20376](https://insights.sbomify.com/CVE-2024-20376/): Denial of service in Cisco IP Phones with Multiplatform Firmware (high 7.5)
- [CVE-2024-20378](https://insights.sbomify.com/CVE-2024-20378/): Missing authorization in Cisco IP Phones with Multiplatform Firmware (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-20357 is a medium-severity memory corruption vulnerability in Cisco IP Phones with Multiplatform Firmware, published on 1 May 2024. 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-2024-20357 in the wild and no public exploit code.

Affected product: Cisco IP Phones with Multiplatform Firmware. 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-20357/ (Markdown: https://insights.sbomify.com/CVE-2024-20357/index.md)
```

## Sources

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

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