# CVE-2024-20378: Missing authorization in Cisco IP Phones with Multiplatform Firmware

> Unauthenticated attackers can access sensitive data and credentials on Cisco IP Phones due to missing authentication on management endpoints.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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-q87c-gjjf-xqfw

## What is CVE-2024-20378?

CVE-2024-20378 is a high-severity missing authorization 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 web-based management interface of Cisco IP Phone firmware could allow an unauthenticated, remote attacker to retrieve sensitive information from an affected device.  

 This vulnerability is due to a lack of authentication for specific endpoints of the web-based management interface on an affected device. An attacker could exploit this vulnerability by connecting to the affected device. A successful exploit could allow the attacker to gain unauthorized access to the device, enabling the recording of user credentials and traffic to and from the affected device, including VoIP calls that could be replayed.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

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

It affects 15 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 7841 With Multiplatform Firmware, Cisco Ip Phone 7861 With Multiplatform Firmware, Cisco Ip Phone 8811 With Multiplatform Firmware, Cisco Ip Phone 8841 With Multiplatform Firmware, Cisco Ip Phone 8851 With Multiplatform Firmware, Cisco Ip Phone 8851nr With Multiplatform Firmware, Cisco Ip Phone 8861 With Multiplatform Firmware, Cisco Video Phone 8875 With Multiplatform Firmware.

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

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

## Is CVE-2024-20378 being exploited?

There is no known exploitation of CVE-2024-20378 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-20357](https://insights.sbomify.com/CVE-2024-20357/): Memory corruption in Cisco IP Phones with Multiplatform Firmware (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-20378 is a high-severity missing authorization 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-20378 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-20378/ (Markdown: https://insights.sbomify.com/CVE-2024-20378/index.md)
```

## Sources

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

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