# CVE-2023-27105: Path traversal in n/a

> Attackers can read, delete, or modify critical system files on Shanling portable music players via directory traversal in the Wi-Fi file transfer module.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2023
- **Updated:** 3 Feb 2025
- **Also known as:** GHSA-6jx7-59gp-6894

## What is CVE-2023-27105?

CVE-2023-27105 is a critical path traversal vulnerability in n/a, published on 25 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the Wi-Fi file transfer module of Shanling M5S Portable Music Player with Shanling MTouch OS v4.3 and Shanling M2X Portable Music Player with Shanling MTouch OS v3.3 allows attackers to arbitrarily read, delete, or modify any critical system files via directory traversal.

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

## Which versions are affected by CVE-2023-27105?

It affects 2 products.


Products: Shanling Eddict Player, Shanling Mtouch Os.

## How do I fix CVE-2023-27105?

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

## Is CVE-2023-27105 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27105 and fix it if it is affected.

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

## Sources

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

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