UnixwareApplication · Caldera

CVE-2002-0679

HIGH · 10.0 CVSS v2.0 Published 2002-09-05
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 overflow in Common Desktop Environment (CDE) ToolTalk RPC database server (rpc.ttdbserverd) allows remote attackers to execute arbitrary code via an argument to the _TT_CREATE_FILE procedure.

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

A detailed technical summary for this CVE is being prepared.

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
UnixwareApplication
Affected:= 7.0= 7.1.0= 7.1.1
DextopApplication
Affected:= 2.1
OpenunixOperating system
Affected:= 8.0
Tru64Operating system
Affected:= 4.0f= 4.0g= 5.0a= 5.1= 5.1a
Hp UxOperating system
Affected:= 10.10= 10.20= 10.24= 11.00= 11.11
AixOperating system
Affected:= 4.3.3= 5.1
SolarisOperating system
Affected:= 2.6= 9.0
SunosOperating system
Affected:= 5.5.1= 5.7= 5.8

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

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.kb.cert.org →
Recommended fix High confidence

Upgrade to vendor-supported operating system versions that include this security fix. For Solaris, upgrade from 2.6/9.0 to Solaris 10 or later with latest patches. For HP-UX, upgrade to HP-UX 11i or later. For AIX, upgrade to AIX 5.2 or later with appropriate ML.

  1. 1. Identify if the rpc.ttdbserverd (ToolTalk) service is running on affected systems: rpcinfo -p | grep ttdbserverd
  2. 2. If the service is not required, disable it to eliminate the attack vector
  3. 3. To disable the service, comment out or remove the ttdbserverd entry from /etc/inetd.conf or /etc/rpc, then restart inetd: kill -HUP <inetd_pid>
  4. 4. Alternatively, for systems using SMF (Solaris 10+), disable the service: svcadm disable svc:/network/rpc/ttdbserverd
  5. 5. If the service is required, apply vendor-specific patches from CERT/CC VU#387387 (http://www.kb.cert.org/vuls/id/387387)
  6. 6. Implement network-level filtering to restrict access to RPC port 111 and the ttdbserverd service port
  7. 7. Use firewall rules (iptables, ipfilter, or native OS firewall) to allow only trusted IPs to connect to RPC services
Caveat Upgrading from end-of-life OS versions (Solaris 2.6, HP-UX 10.x, AIX 4.3.3) to supported versions may require significant application compatibility testing and could introduce breaking changes in application behavior.

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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