CVE-2000-0781
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unediteduagentsetup 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe uagentsetup utility in ARCServeIT Client Agent 6.62 suffers from a time-of-check-time-of-use (TOCTOU) race condition when handling a temporary file that gets moved to the agent.cfg configuration file. The application fails to verify file existence or ownership before the move operation, allowing a local attacker to substitute a malicious file via symlink or pre-existing file manipulation and achieve arbitrary command execution with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.63_linuxCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Ca Arcserve Backup is installedLocate the Ca Arcserve Backup installation directory and identify the installed version by querying the package or binary version informationAffected if The installed version is 6.63_linux
-
Verify the uagentsetup utility is presentSearch for the uagentsetup or uagentsetup.exe binary in the installation directory, typically under the Client Agent or agent subdirectoryAffected if The uagentsetup utility exists and is executable in the expected installation path
-
Identify the agent working directoryLocate the directory where uagentsetup creates temporary files and where agent.cfg is stored. Common paths include /opt/caarcserve/ or installation-root directoriesAffected if A working directory containing agent.cfg and temporary file handling is present
-
Inspect filesystem permissions on the agent directoryUse 'ls -la' or equivalent command to list ownership and permissions on the directory where uagentsetup operates and creates temporary filesAffected if The directory has weak permissions allowing untrusted users to create or modify files (world-writable or owned by a different user than the agent runs as)
-
Check for symlinks in the working directoryUse 'ls -la' and 'find' commands to identify any symbolic links pointing to the agent.cfg file or temporary files in the agent working directoryAffected if Symlinks exist that could redirect the temporary file or agent.cfg to an attacker-controlled location
A system is affected if Ca Arcserve Backup version 6.63_linux is installed, the uagentsetup utility is present, and the agent working directory has weak permissions allowing untrusted file manipulation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThis vulnerability affects a 2000-era legacy application that is likely end-of-life. Organizations should identify and remove affected installations if possible. If continued use is required, implement strict filesystem controls around the agent working directory to prevent untrusted file manipulation, or replace the software with a supported alternative.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0781 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2000-0781 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data