# CVE-2024-32944: Path traversal in UTAU

> Attackers can place arbitrary files via crafted voicebank installers, requiring users to install malicious packages.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 May 2024
- **Updated:** 29 Oct 2024

## What is CVE-2024-32944?

CVE-2024-32944 is a low-severity path traversal vulnerability in ameya/ayame UTAU, published on 28 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Path traversal vulnerability exists in UTAU versions prior to v0.4.19. If a user of the product installs a crafted UTAU voicebank installer (.uar file, .zip file) to UTAU, an arbitrary file may be placed.

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

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


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

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

## Is CVE-2024-32944 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32944 is a low-severity path traversal vulnerability in ameya/ayame UTAU, published on 28 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-32944 in the wild and no public exploit code.

Affected product: ameya/ayame UTAU. 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-32944/ (Markdown: https://insights.sbomify.com/CVE-2024-32944/index.md)
```

## Sources

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

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