# CVE-2024-28065: Information disclosure in n/a

> Unencrypted firmware files expose sensitive data like root password hashes, allowing attackers to gain privileged access to Unify CP IP Phones.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Apr 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-c8c6-87mv-3fm9

## What is CVE-2024-28065?

CVE-2024-28065 is a medium-severity vulnerability in n/a, published on 5 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Unify CP IP Phone firmware 1.10.4.3, files are not encrypted and contain sensitive information such as the root password hash.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2024-28065 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28065 is a medium-severity vulnerability in n/a, published on 5 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-28065 in the wild and no public exploit code.

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-28065/ (Markdown: https://insights.sbomify.com/CVE-2024-28065/index.md)
```

## Sources

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

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