# CVE-2003-0596: Race condition in n/a

> Local attackers can read or modify other users' files by exploiting predictable temporary directory names in FDclone.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:P/I:P/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:** Yes
- **Published:** 25 Jul 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0596, DSA-352, GHSA-3gjm-xjgf-753r

## What is CVE-2003-0596?

CVE-2003-0596 is a low-severity vulnerability in n/a, published on 25 Jul 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

FDclone 2.00a, and other versions before 2.02a, creates temporary directories with predictable names and uses them if they already exist, which allows local users to read or modify files of other fdclone users by creating the directory ahead of time.

## Which versions are affected by CVE-2003-0596?

It affects 1 product.


Products: Fdclone Fdclone.

## How do I fix CVE-2003-0596?

Upgrade to a fixed version.

## Is CVE-2003-0596 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0596 and fix it if it is affected.

What it is: CVE-2003-0596 is a low-severity vulnerability in n/a, published on 25 Jul 2003. 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-2003-0596 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-2003-0596/ (Markdown: https://insights.sbomify.com/CVE-2003-0596/index.md)
```

## Sources

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

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