DmailApplication · Netwin

CVE-2001-1355

HIGH · 10.0 CVSS v2.0 Published 2001-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Buffer overflows in NetWin Authentication Module (NWAuth) 3.0b and earlier, as implemented in DMail, SurgeFTP, and possibly other packages, could allow attackers to execute arbitrary code via long arguments to (1) the -del command or (2) the -lookup 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

Buffer overflow vulnerabilities in NetWin Authentication Module (NWAuth) versions 3.0b and earlier allow remote attackers to execute arbitrary code by supplying excessively long arguments to the -del and -lookup command parameters. This affects DMail, SurgeFTP, and potentially other NetWin products that incorporate the vulnerable NWAuth module.

MitigationUpgrade NWAuth to a version newer than 3.0b, or apply vendor-provided patches. If no patch is available, disable or restrict access to the affected command-line interfaces and consider network segmentation to limit exposure.

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
DmailApplication
Affected:= 2.5d= 2.7= 2.7q= 2.7r= 2.8e= 2.8f= 2.8g= 2.8h= 2.8i
SurgeftpApplication
Affected:= 1.0b= 2.0a= 2.0b

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
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/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 checks

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

  1. Identify installed NetWin products
    Check for DMail or SurgeFTP installations on the system. Look for executables or services named 'dmail', 'surgeftp', or 'nwauth' in common installation directories such as /usr/local/bin, /usr/sbin, or the program's default installation path.
    Affected if Either DMail or SurgeFTP is installed on the system
  2. Determine installed software version
    Run the installed product with a version flag (common flags include -v, -version, or checking the binary directly). For DMail, check the version banner at startup. For SurgeFTP, use 'surgeftp -v' or check the version information in the administration interface.
    Affected if The installed version matches or is earlier than the affected versions (Dmail: 2.5d through 2.8i, Surgeftp: 1.0b through 2.0b)
  3. Locate NWAuth module
    Search for the NWAuth executable or library file on the system. It may be present as 'nwauth', 'NWAuth', or part of the DMail/SurgeFTP installation directory. Check process list for any running nwauth daemon or service.
    Affected if The NWAuth module (version 3.0b or earlier) is present on the system
  4. Verify command interface exposure
    Determine if the command-line interface accepting -del and -lookup parameters is accessible. This typically involves NWAuth being run as a daemon or being invoked by the parent NetWin product. Check configuration files or documentation for how NWAuth is invoked.
    Affected if NWAuth is running and exposes the -del or -lookup command parameters to external input

A system is affected if it runs any version of NetWin DMail (2.5d through 2.8i) or SurgeFTP (1.0b through 2.0b) with the NWAuth module (version 3.0b or earlier) that exposes the -del or -lookup command interface.

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

Upgrade NWAuth to a version newer than 3.0b, or apply vendor-provided patches. If no patch is available, disable or restrict access to the affected command-line interfaces and consider network segmentation to limit exposure.

Fix this in Dmail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2001-1355 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2001-1355 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