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

> A local attacker can exploit insecure temporary file handling to overwrite files or inject code into the Wine registry via symlink attacks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2023
- **Updated:** 24 Sep 2024
- **Also known as:** GHSA-pv97-pjxj-gx6w

## What is CVE-2023-43783?

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

### Official description

Cadence through 0.9.2 2023-08-21 uses an Insecure /tmp/cadence-wineasio.reg Temporary File. The filename is used even if it has been created by a local adversary before Cadence started. The adversary can leverage this to create or overwrite files via a symlink attack. In some kernel configurations, code injection into the Wine registry is possible.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 1 product.


Products: Falktx Cadence.

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

Apply the vendor's patch.

## Is CVE-2023-43783 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-43782](https://insights.sbomify.com/CVE-2023-43782/): Race condition in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43783 is a high-severity path traversal vulnerability in n/a, published on 22 Sep 2023. 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-2023-43783 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-2023-43783/ (Markdown: https://insights.sbomify.com/CVE-2023-43783/index.md)
```

## Sources

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

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