# CVE-2023-42487: Soundminer – CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

> Attackers can exploit a path traversal vulnerability in Soundminer to read or modify files outside the intended directory.

- **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:** 27 Sep 2023
- **Updated:** 23 Sep 2024
- **Also known as:** GHSA-4c8h-hw7r-25rm

## What is CVE-2023-42487?

CVE-2023-42487 is a high-severity path traversal vulnerability in Soundminer, published on 27 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Soundminer – CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

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

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

It affects 1 product.


Products: Soundminer Soundminer.

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

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

## Is CVE-2023-42487 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42487 is a high-severity path traversal vulnerability in Soundminer, published on 27 Sep 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-42487 in the wild and no public exploit code.

Affected product: Soundminer. 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-42487/ (Markdown: https://insights.sbomify.com/CVE-2023-42487/index.md)
```

## Sources

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

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