dbcve.org
Tru64Operating system · Compaq

CVE-2002-2003

MEDIUM · 5.0 CVSS v2.0 Published 2002-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
ypbind in Compaq Tru64 4.0F, 4.0G, 5.0A, 5.1 and 5.1A allows remote attackers to cause the process to core dump via certain network packets generated by nmap.

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

ypbind (Yellow Pages bind service) on Compaq Tru64 UNIX versions 4.0F through 5.1A contains a vulnerability where specially crafted network packets (such as those generated by nmap port scans) can cause the ypbind process to crash and generate a core dump, resulting in a denial of service condition.

MitigationThis affects legacy Tru64 systems no longer in mainstream support; primary remediation is upgrading to a supported OS or implementing network access controls to restrict unauthorized scanning/queries to the ypbind service.

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
Tru64Operating system
Affected:= 4.0f= 4.0g= 5.0a= 5.1= 5.1a

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
Partial
Integrity
None
Availability
None

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

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

  1. Identify the operating system version
    Run 'uname -a' or 'cat /etc/os-release' to determine the Tru64 version
    Affected if The version matches 4.0f, 4.0g, 5.0a, 5.1, or 5.1a
  2. Verify ypbind is installed
    Check for the presence of the ypbind binary using 'which ypbind' or 'ls /usr/sbin/ypbind'
    Affected if ypbind binary exists on the system
  3. Confirm ypbind is running
    Run 'ps -ef | grep ypbind' to check for active ypbind processes
    Affected if A ypbind process is currently running
  4. Determine ypbind network exposure
    Run 'netstat -an | grep ypbind' or 'ypcat -x' to see if ypbind is bound to network ports and accessible
    Affected if ypbind is listening on network ports and accepting remote connections

You are affected if you are running Compaq Tru64 versions 4.0f through 5.1a with the ypbind service running and network-accessible.

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

This affects legacy Tru64 systems no longer in mainstream support; primary remediation is upgrading to a supported OS or implementing network access controls to restrict unauthorized scanning/queries to the ypbind service.

Fix this in Tru64 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-2003 — 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-2002-2003 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