CVE-1999-0076
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 · uneditedBuffer overflow in wu-ftp from PASV command causes a core dump.
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 confidenceBuffer overflow vulnerability in wu-ftpd server triggered by the PASV command, which is used to establish FTP passive mode connections. The overflow causes the server to crash and dump core, indicating potential for denial of service and possibly remote code execution depending on exploitation sophistication.
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.
-
Check if wu-ftpd is installedRun 'rpm -qa | grep wu-ftpd' or 'dpkg -l | grep wu-ftpd' depending on your package manager, or check for the binary at /usr/sbin/wu-ftpd or /usr/sbin/ftpdAffected if wu-ftpd package or binary is found on the system
-
Identify the wu-ftpd versionRun 'wuftpd -v' or check the RPM/Deb package version with 'rpm -q wu-ftpd' or 'dpkg -s wu-ftpd'Affected if Any version is returned, as all versions of wu-ftpd are affected by this vulnerability
-
Verify the FTP server is running and enabledRun 'ps aux | grep wu.ftpd' or 'systemctl status vsftpd' (note: wu-ftpd may run as inetd/xinetd service, check /etc/inetd.conf or /etc/xinetd.d/wu-ftpd)Affected if wu-ftpd daemon or service is actively running
-
Check if FTP port 21 is exposed to networkRun 'netstat -tlnp | grep :21' or 'ss -tlnp | grep :21' to see if port 21 is listening, then verify firewall rules with 'iptables -L' or 'firewall-cmd --list-all' to determine if it is accessible from untrusted networksAffected if FTP port 21 is listening and accessible from networks beyond trusted local segments
If wu-ftpd is installed, running, and network-accessible on port 21, the environment is affected by this vulnerability since all versions of wu-ftpd contain the buffer overflow in the PASV command handler.
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 dataUpdate wu-ftpd to a patched version if available, or migrate to a maintained FTP server implementation. If wu-ftpd must remain in use, restrict FTP access to trusted networks and monitor for exploitation attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-1999-0076 — 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-1999-0076 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