CVE-2001-1587
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 · uneditedNWFTPD.nlm before 5.01w in the FTP server in Novell NetWare allows remote attackers to cause a denial of service (abend) via an anonymous STOU command.
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 confidenceNWFTPD.nlm, the FTP server component for Novell NetWare, mishandles the STOU (store unique) command when executed by anonymous users. This causes the server to abend (abort and terminate), resulting in a denial of service. The vulnerability exists in versions prior to 5.01w.
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 dataall versionsCVSS 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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.
-
Confirm NWFTPD.nlm is loadedAt the NetWare server console, type 'modules nwftpd.nlm' or check the System Console log for NWFTPD.nlm loading messagesAffected if NWFTPD.nlm is not loaded on the system
-
Check NWFTPD.nlm versionAt the NetWare console, type 'modules nwftpd.nlm' to display version information, or inspect the file version property of NWFTPD.nlm in the SYS:SYSTEM directoryAffected if The version displayed is earlier than 5.01w (for example, 5.00, 4.x, or any version number below 5.01w)
-
Verify anonymous FTP access is enabledCheck the FTP server configuration files (typically FTPSTATS.NCF or FTP daemon configuration) for anonymous user settings, or use the NetWare Administrator utility to check FTP access rightsAffected if Anonymous FTP access is enabled and anonymous users can connect to the FTP server
-
Confirm STOU command is available to anonymous usersAttempt to connect to the FTP server as an anonymous user (login: anonymous, password: any email address) and issue the STOU command, or review FTP server access control settings that define which commands are allowed for anonymous sessionsAffected if Anonymous users can execute the STOU command on the FTP server
The system is affected if NWFTPD.nlm version below 5.01w is loaded AND anonymous FTP access is enabled, allowing anonymous users to trigger the STOU command and cause server abend.
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 dataUpgrade NWFTPD.nlm to version 5.01w or later. Alternatively, disable or restrict anonymous FTP access until the patch can be applied.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-1587 — 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-1587 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