# CVE-2024-28066: Hardcoded credentials in n/a

> Attackers can gain root access to Unify CP IP Phones using hardcoded credentials, leading to full device compromise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2024
- **Updated:** 15 Aug 2024
- **Also known as:** GHSA-pxfw-cxx3-vxv8

## What is CVE-2024-28066?

CVE-2024-28066 is a high-severity vulnerability in n/a, published on 8 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Unify CP IP Phone firmware 1.10.4.3, Weak Credentials are used (a hardcoded root password).

Weakness: CWE-259 (Use of Hard-coded Password), CWE-1391 (Use of Weak Credentials)

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

It affects 14 products.


Products: Mitel 6905 Firmware, Mitel 6910 Firmware, Mitel 6915 Firmware, Mitel 6920w Firmware, Mitel 6930w Firmware, Mitel 6940w Firmware, Mitel 6970 Firmware, Mitel 700d Dect Firmware, Mitel Openscape Cp110 Firmware, Mitel Openscape Cp210 Firmware, Mitel Openscape Cp410 Firmware, Mitel Openscape Cp710 Firmware, Mitel Openscape Cpx10 Firmware, Mitel Openscape Dect Firmware.

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

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

## Is CVE-2024-28066 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28066 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28066 is a high-severity vulnerability in n/a, published on 8 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28066 exists.

Affected product: n/a. 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-28066/ (Markdown: https://insights.sbomify.com/CVE-2024-28066/index.md)
```

## Sources

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

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