# CVE-2023-29586: Missing authorization in n/a

> TeraCopy allows arbitrary file reads via improper access validation during copy operations, though the vendor disputes this claim.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** No
- **Published:** 19 Apr 2023
- **Updated:** 5 Feb 2025
- **Also known as:** GHSA-xcx3-wvhg-c3h3

## What is CVE-2023-29586?

CVE-2023-29586 is a medium-severity missing authorization vulnerability in n/a, published on 19 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Code Sector TeraCopy 3.9.7 does not perform proper access validation on the source folder during a copy operation. This leads to Arbitrary File Read by allowing any user to copy any directory in the system to a directory they control. NOTE: the Supplier disputes this because only admin users can copy arbitrary folders, and because the 143984 reference is about a different concern (unrelated to directory copying) that was fixed in 3.5b.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Codesector Teracopy.

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

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

## Is CVE-2023-29586 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-29586 is a medium-severity missing authorization vulnerability in n/a, published on 19 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-29586 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-29586/ (Markdown: https://insights.sbomify.com/CVE-2023-29586/index.md)
```

## Sources

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

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