# CVE-2024-28442: Path traversal in n/a

> A physically proximate attacker can exploit a directory traversal flaw in the Yealink VP59 to access sensitive information via the terms of use function.

- **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:** 26 Mar 2024
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-56rx-5jgh-c8q2

## What is CVE-2024-28442?

CVE-2024-28442 is a high-severity path traversal vulnerability in n/a, published on 26 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory Traversal vulnerability in Yealink VP59 v.91.15.0.118 allows a physically proximate attacker to obtain sensitive information via terms of use function in the company portal component.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Yealink Vp59 Firmware.

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

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

## Is CVE-2024-28442 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-30939](https://insights.sbomify.com/CVE-2024-30939/): Auth bypass in n/a (medium 6.8)
- [CVE-2024-31747](https://insights.sbomify.com/CVE-2024-31747/): Security feature bypass in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28442 is a high-severity path traversal vulnerability in n/a, published on 26 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28442 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-28442/ (Markdown: https://insights.sbomify.com/CVE-2024-28442/index.md)
```

## Sources

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

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