# CVE-2023-43782: Race condition in n/a

> A local attacker can disrupt Cadence by pre-creating or deleting a specific temporary file, causing a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2023
- **Updated:** 24 Sep 2024
- **Also known as:** GHSA-353r-fqp4-g8f7

## What is CVE-2023-43782?

CVE-2023-43782 is a medium-severity vulnerability in n/a, published on 22 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cadence through 0.9.2 2023-08-21 uses an Insecure /tmp/.cadence-aloop-daemon.x Temporary File. The file is used even if it has been created by a local adversary before Cadence started. The adversary can then delete the file, disrupting Cadence.

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

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

It affects 1 product.


Products: Falktx Cadence.

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

Apply the vendor's patch.

## Is CVE-2023-43782 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-43783](https://insights.sbomify.com/CVE-2023-43783/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43782 is a medium-severity vulnerability in n/a, published on 22 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43782 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-43782/ (Markdown: https://insights.sbomify.com/CVE-2023-43782/index.md)
```

## Sources

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

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