# CVE-2000-0781: Race condition in n/a

> Local attackers can execute arbitrary commands by exploiting a race condition in temporary file handling during agent setup.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-fq8g-x6c4-fpm3

## What is CVE-2000-0781?

CVE-2000-0781 is a high-severity vulnerability in n/a, published on 1 Sep 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

uagentsetup in ARCServeIT Client Agent 6.62 does not properly check for the existence or ownership of a temporary file which is moved to the agent.cfg configuration file, which allows local users to execute arbitrary commands by modifying the temporary file before it is moved.

## Which versions are affected by CVE-2000-0781?

It affects 1 product.


Products: Ca Arcserve Backup.

## How do I fix CVE-2000-0781?

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

## Is CVE-2000-0781 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1761](https://insights.sbomify.com/CVE-2009-1761/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0781 and fix it if it is affected.

What it is: CVE-2000-0781 is a high-severity vulnerability in n/a, published on 1 Sep 2004. 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-2000-0781 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-2000-0781/ (Markdown: https://insights.sbomify.com/CVE-2000-0781/index.md)
```

## Sources

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

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