Debian LinuxOperating system · Debian
CVE-2000-0107
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 · uneditedLinux apcd program allows local attackers to modify arbitrary files via a symlink attack.
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 · moderate confidenceThe apcd (APC daemon) program on Linux systems contains a symlink vulnerability that allows local attackers to create or modify arbitrary files by exploiting a time-of-check-time-of-use (TOCTOU) race condition when the daemon creates files in world-writable directories. Attackers can intercept file creation via symbolic links to redirect writes to sensitive system files.
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
Debian LinuxOperating system
= 2.1CVSS 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.
-
Determine if the apcd (APC daemon) package is installedQuery the package manager for the apcd package (e.g., dpkg -l apcd or rpm -qa | grep apcd)Affected if The apcd package is installed on Debian Linux 2.1
-
Identify the installed apcd versionRun 'dpkg -l apcd' or check /var/lib/dpkg/info/apcd.list for version informationAffected if The installed version matches Debian Linux 2.1 exactly (version = 2.1)
-
Verify if apcd is currently runningCheck running processes for apcd (e.g., ps aux | grep apcd or pgrep apcd)Affected if apcd daemon is actively running on the system
-
Locate directories where apcd creates temporary files or log filesReview apcd configuration files (typically in /etc or /var) and monitor file creation behavior during daemon operationAffected if apcd writes files to world-writable directories (common targets: /tmp, /var/tmp, or similar)
A system is affected if it runs apcd from Debian Linux 2.1, the daemon is actively running, and it creates files in world-writable directories where symlink attacks could redirect file writes to sensitive locations.
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 dataRemediate by implementing safe temporary file creation practices (O_EXCL flag, mkstemp()) in apcd, removing world-writable permissions from affected directories, or upgrading to a patched version of the software if available.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0107 — 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-0107 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