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

> Attackers can overwrite arbitrary files on Tiptel IP 286 phones via the web interface ringtone upload function.

- **Severity:** Critical 9.9 (`CVSS:3.1/AC:L/AV:N/A:L/C:H/I:H/PR:L/S:C/UI: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:** 19 Sep 2024
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-2hc5-mf64-rr7f

## What is CVE-2024-33109?

CVE-2024-33109 is a critical path traversal vulnerability in n/a, published on 19 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory Traversal in the web interface of the Tiptel IP 286 with firmware version 2.61.13.10 allows attackers to overwrite arbitrary files on the phone via the Ringtone upload function.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 2 products.


Products: Ergophone Tiptel Ip 286 Firmware, Yealink Sip-T28p Firmware.

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

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

## Is CVE-2024-33109 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-33109 is a critical path traversal vulnerability in n/a, published on 19 Sep 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-33109 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-33109/ (Markdown: https://insights.sbomify.com/CVE-2024-33109/index.md)
```

## Sources

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

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