CVE-2001-1435
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 · uneditedinetd in Compaq Tru64 UNIX 5.1 allows attackers to cause a denial of service (network connection loss) by causing one of the services handled by inetd to core dump during startup, which causes inetd to stop accepting connections to all of its services.
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 confidenceInetd (internet daemon) in Compaq Tru64 UNIX 5.1 contains a design flaw where if any service it manages crashes/core dumps during startup, inetd itself terminates and stops accepting connections for ALL services. This is a denial-of-service vulnerability where individual service failures cascade to affect the entire inetd-managed service infrastructure.
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.1CVSS 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.
-
Identify the operating system versionRun 'uname -a' or 'cat /etc/os-release' to confirm the OS is Compaq Tru64 UNIX 5.1Affected if The OS is NOT Tru64 UNIX 5.1 - the vulnerability only applies to this specific version
-
Confirm inetd is runningCheck for inetd processes using 'ps -ef | grep inetd' or check /proc for inetd processesAffected if inetd is not running - no inetd-managed services exist, so the cascade failure cannot occur
-
Verify inetd configuration existsCheck for /etc/inetd.conf or /etc/xinetd.d/ directory to confirm inetd manages servicesAffected if No inetd configuration found - inetd is not managing any services, so the design flaw cannot be triggered
-
Check for active managed servicesReview inetd configuration to list all services currently configured under inetd managementAffected if No services are configured under inetd - the cascade failure has no mechanism to trigger since no service can crash during startup
You are affected if you are running Compaq Tru64 UNIX 5.1 with inetd actively managing one or more services, as the design flaw allows any single service crash during startup to terminate inetd and disrupt all services.
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 dataSince Tru64 UNIX 5.1 is a legacy system likely no longer supported, remediation options include: replacing inetd with a more robust daemon manager (like xinetd), implementing process monitoring to auto-restart inetd on failure, or using network-level rate limiting to prevent the attack vector. Upgrade or decommission if possible.
- 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-2001-1435 — 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-2001-1435 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