CVE-2002-2434
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.02i in the FTP server in Novell NetWare does not properly listen for data connections, which allows remote attackers to cause a denial of service (abend) via multiple FTP sessions.
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 confidenceNWFTPD.nlm (the FTP server for Novell NetWare) versions prior to 5.02i contain a flaw in how the server listens for data connections during FTP sessions. When multiple FTP sessions are established, the server fails to properly handle data connection listening, causing the NetWare system to abend (abnormal end/crash), resulting in denial of service.
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<= 5.02b= 5.01i= 5.01o= 5.01w= 5.01y= 5.1= 6.0= 6.5CVSS 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.
-
Verify NWFTPD.nlm is loadedCheck the loaded modules on the NetWare server using the appropriate system console command or management interface to confirm NWFTPD.nlm is currently activeAffected if NWFTPD.nlm is not loaded means the vulnerability does not apply; if loaded, proceed to version check
-
Determine NWFTPD.nlm versionUse the NetWare console or NLM management tools to query the loaded version of NWFTPD.nlmAffected if Version is 5.02b or earlier, OR exactly 5.01i, 5.01o, 5.01w, or 5.01y indicates the vulnerable version is present
-
Confirm NetWare system versionCheck the operating system version of the NetWare serverAffected if Running NetWare 5.1, 6.0, or 6.5 in combination with a vulnerable NWFTPD.nlm version places the system within the affected product range
-
Verify FTP server is enabledConfirm that the FTP server service is actively listening and accepting connections on the systemAffected if The vulnerability only triggers when the FTP server is running and handling sessions; if FTP is disabled, the flaw cannot be exploited
-
Check for active FTP sessionsMonitor the FTP server for multiple concurrent session handlingAffected if The flaw manifests specifically when multiple FTP sessions are established simultaneously, causing the data connection listening failure and system abend
A system is affected if it runs NWFTPD.nlm version 5.02b or earlier (or 5.01i/o/w/y) on NetWare 5.1, 6.0, or 6.5, with the FTP server enabled and capable of handling multiple concurrent FTP sessions.
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.02i or later, which contains the corrected data connection handling logic. If upgrading is not feasible, consider restricting or filtering FTP access at the network perimeter to limit exposure to the vulnerability.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-2434 — 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-2002-2434 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