dbcve.org
Hp UxOperating system · Hp

CVE-2002-1614

HIGH · 7.2 CVSS v2.0 Published 2002-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Buffer overflow in HP Tru64 UNIX allows local users to execute arbitrary code via a long argument to /usr/bin/at.

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

Buffer overflow in HP Tru64 UNIX /usr/bin/at allows local users to execute arbitrary code via a long argument, typically enabling local privilege escalation to root or elevated privileges.

MitigationApply HP security patches for Tru64 UNIX; if patches are unavailable, restrict or disable /usr/bin/at access for untrusted local users.

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
Hp UxOperating system
Affected:= 10.20= 11.00= 11.04= 11.11= 11.22
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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

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
    Run 'uname -a' or check /etc/os-release to confirm if the system is HP-UX or Tru64 UNIX
    Affected if The system is running HP-UX (any of versions 10.20, 11.00, 11.04, 11.11, 11.22) or Tru64 UNIX (any of versions 4.0f, 4.0g, 5.0a, 5.1, 5.1a)
  2. Check installed HP-UX version
    Run 'uname -a' or 'swlist -l bundle' to determine the exact HP-UX version
    Affected if The version matches 10.20, 11.00, 11.04, 11.11, or 11.22
  3. Check installed Tru64 version
    Run 'uname -a' or check '/usr/sbin/sizer -v' to determine the Tru64 version
    Affected if The version matches 4.0f, 4.0g, 5.0a, 5.1, or 5.1a
  4. Verify /usr/bin/at exists
    Run 'ls -la /usr/bin/at' to confirm the at binary is present
    Affected if The file /usr/bin/at exists on the system
  5. Check /usr/bin/at permissions and ownership
    Run 'ls -la /usr/bin/at' to inspect permissions. The vulnerability is exploitable if any untrusted local user can execute this binary
    Affected if The at binary is readable and executable by untrusted local users (not restricted to root only)

A system is affected if it runs HP-UX versions 10.20 through 11.22 or Tru64 versions 4.0f through 5.1a and has the /usr/bin/at binary accessible to untrusted local users.

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

Apply HP security patches for Tru64 UNIX; if patches are unavailable, restrict or disable /usr/bin/at access for untrusted local users.

Fix this in Hp Ux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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