CVE-1999-0035
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 · uneditedRace condition in signal handling routine in ftpd, allowing read/write arbitrary files.
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 confidenceRace condition in the signal handling routine of ftpd allows local or remote attackers to read/write arbitrary files on the system due to a time-of-check-time-of-use (TOCTOU) vulnerability in how signals are handled during file operations.
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.01all 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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.
-
Identify the ftpd daemon in useRun 'ps aux | grep ftpd' or 'which ftpd' to find the running FTP daemon binaryAffected if The ftpd binary is from Gnu Inet version 5.01 or is the native ftpd on Sgi IRIX systems (any version)
-
Check the ftpd versionRun 'ftpd -v' or check the binary version with 'ftpwho' or by inspecting the binary with 'strings' if version flags are unavailableAffected if Version is Gnu Inet 5.01 or the system is running Sgi IRIX with any ftpd version
-
Determine if anonymous FTP access is enabledCheck for 'anonymous' user in /etc/passwd and review ftpd configuration files (e.g., /etc/ftpusers, /etc/ftpd/ftpaccess) for 'anonymous' or 'anon' settingsAffected if Anonymous FTP access is enabled, making the system remotely exploitable via this vulnerability
-
Inspect FTP server configuration for writable directoriesReview ftpd config for 'write' or 'upload' permissions, check for 'chmod' or 'umask' settings that allow file creation in accessible directoriesAffected if FTP server is configured with writable directories that unauthenticated or anonymous users can access
You are affected if you are running Gnu Inet ftpd version 5.01 or any ftpd on Sgi IRIX, particularly with anonymous FTP or writable directory configurations enabled.
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 or replace the vulnerable ftpd daemon with a patched version or modern secure alternative (e.g., vsftpd, ProFTPD with security configurations); restrict or disable anonymous FTP access until remediation is complete.
- 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-0035 — 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-0035 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