dbcve.org
TruclusterApplication · Compaq

CVE-2001-1033

MEDIUM · 5.0 CVSS v2.0 Published 2001-09-25
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
Compaq TruCluster 1.5 allows remote attackers to cause a denial of service via a port scan from a system that does not have a DNS PTR record, which causes the cluster to enter a "split-brain" state.

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 · low confidence

Compaq TruCluster 1.5 enters a 'split-brain' state when a port scan is performed from a system lacking a DNS PTR record. This causes cluster nodes to lose proper communication, resulting in a denial of service.

MitigationEnsure all systems performing network operations against the cluster have valid DNS PTR records configured, or upgrade to a supported cluster solution as TruCluster 1.5 is obsolete legacy software.

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
TruclusterApplication
Affected:= 1.5
Tru64Operating system
Affected:= 5.0= 5.1

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
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 checks

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

  1. Identify TruCluster version
    Run 'cluster show status' or check system documentation to confirm TruCluster version is exactly 1.5
    Affected if TruCluster version equals 1.5
  2. Identify Tru64 version
    Run 'uname -a' or check system properties to confirm Tru64 version is exactly 5.0 or 5.1
    Affected if Tru64 version equals 5.0 or 5.1
  3. Verify DNS PTR records for external systems
    For each system that may perform network operations or port scans against the cluster, verify that a valid DNS PTR record exists using 'nslookup <IP>' or 'dig -x <IP>'
    Affected if Any system performing port scans or network operations against the cluster lacks a DNS PTR record

You are affected if you run TruCluster 1.5 or Tru64 5.0/5.1 AND a system without a DNS PTR record performs a port scan or network operation against your cluster, causing split-brain and denial of service.

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

Ensure all systems performing network operations against the cluster have valid DNS PTR records configured, or upgrade to a supported cluster solution as TruCluster 1.5 is obsolete legacy software.

Fix this in Trucluster Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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