CVE-2001-0625
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 · uneditedftpdownload in Computer Associates InoculateIT 6.0 allows a local attacker to overwrite arbitrary files via a symlink attack on /tmp/ftpdownload.log .
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 confidenceA local symlink attack vulnerability exists in the ftpdownload component of Computer Associates InoculateIT 6.0. The application writes to /tmp/ftpdownload.log without validating whether the file is a symbolic link, allowing a local attacker to create a symlink from that path to an arbitrary target file, causing the application to overwrite that file with controlled content.
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.0CVSS 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.
-
Verify InoculateIT 6.0 installationLocate the InoculateIT installation directory and check for product executables or services. Common locations may include /opt/CA/InoculateIT or C:\Program Files\CA\InoculateIT on Windows. Look for product binaries or check system inventory tools for the installed product.Affected if Computer Associates InoculateIT is found on the system.
-
Confirm version is exactly 6.0Check the product version using its native version command, about dialog, or by inspecting version information in the installation directory. Compare the installed version against the affected range = 6.0.Affected if The installed version is precisely 6.0.
-
Identify ftpdownload component presenceSearch for the ftpdownload component or executable within the InoculateIT installation directory. This component handles FTP download operations and writes to the log file.Affected if The ftpdownload component exists and is present in the installation.
-
Check for vulnerable log file pathInspect whether /tmp/ftpdownload.log exists on the system. This is the file path the vulnerable component writes to without symlink validation.Affected if The path /tmp/ftpdownload.log is present or creatable by the application.
A system is affected if Computer Associates InoculateIT version 6.0 is installed with the ftpdownload component present, as the application will write to /tmp/ftpdownload.log without validating symlink status, allowing arbitrary file overwrite.
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 is a legacy product from 2001 that is likely End-of-Life with no available patches; the primary remediation is to retire or replace the affected system with a supported solution.
- 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-2001-0625 — 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-2001-0625 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