dbcve.org
Netware Ftp ServerApplication · Novell

CVE-2010-0625

MEDIUM · 6.5 CVSS v2.0 Published 2010-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Stack-based buffer overflow in NWFTPD.nlm before 5.10.01 in the FTP server in Novell NetWare 5.1 through 6.5 SP8 allows remote authenticated users to cause a denial of service (daemon crash) or possibly execute arbitrary code via a long (1) MKD, (2) RMD, (3) RNFR, or (4) DELE 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 confidence

A stack-based buffer overflow vulnerability exists in NWFTPD.nlm (NetWare FTP server) versions before 5.10.01, affecting Novell NetWare 5.1 through 6.5 SP8. The vulnerability is triggered by sending excessively long arguments in MKD, RMD, RNFR, or DELE FTP commands, allowing authenticated remote attackers to crash the service or potentially execute arbitrary code.

MitigationApply the vendor patch (NWFTPD.nlm version 5.10.01 or later) to resolve the buffer overflow. If patching is not feasible, consider restricting FTP access to trusted users only or disabling the FTP service until a patch can be applied.

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
Netware Ftp ServerApplication
Affected:= 5.01i= 5.01o= 5.01w= 5.01y= 5.02b= 5.02i= 5.02r= 5.02y= 5.03b= 5.03l= 5.04.5= 5.04.8
NetwareOperating system
Affected:= 5.1= 6.0= 6.5

CVSS 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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if NWFTPD.nlm is installed
    Check the system for the presence of NWFTPD.nlm file, typically located in the NetWare system directory (e.g., SYS:\SYSTEM\NWFTPD.NLM) or via NetWare administrator console
    Affected if NWFTPD.nlm file exists on the system
  2. Determine NWFTPD.nlm version
    Use NetWare console command to display the NWFTPD.nlm version (e.g., 'modules NWFTPD' or similar command to query loaded NLM module version)
    Affected if Version is before 5.10.01 (including 5.01i, 5.01o, 5.01w, 5.01y, 5.02b, 5.02i, 5.02r, 5.02y, 5.03b, 5.03l, 5.04.5, 5.04.8)
  3. Identify NetWare operating system version
    Check the NetWare OS version via console ('version' command) or admin tools
    Affected if Running NetWare 5.1, 6.0, or 6.5 (any SP level)
  4. Verify FTP service is running
    Check if the FTP server service is active using NetWare console commands (e.g., 'nlist' or 'nss' commands showing loaded services, or check for port 21 listener)
    Affected if FTP service (NWFTPD.nlm) is loaded and running

You are affected if NWFTPD.nlm is installed with a version before 5.10.01 on NetWare 5.1, 6.0, or 6.5 and the FTP service is running.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch (NWFTPD.nlm version 5.10.01 or later) to resolve the buffer overflow. If patching is not feasible, consider restricting FTP access to trusted users only or disabling the FTP service until a patch can be applied.

Fix this in Netware Ftp Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0625 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0625 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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