dbcve.org
Hp UxOperating system · Hp

CVE-1999-0307

HIGH · 7.2 CVSS v2.0 Published 2000-12-20
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-UX cstm program allows local users to gain root privileges.

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 vulnerability in HP-UX cstm (Customer Support Tool Manager) program enables local unprivileged users to execute arbitrary code with root privileges. The flaw stems from improper bounds checking when cstm processes user input, allowing an attacker to overwrite stack memory and gain elevated system access.

MitigationApply HP security patch for cstm or upgrade to a patched HP-UX version; restrict cstm binary permissions to authorized administrators only as an interim control.

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:= 9.00= 10.00

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. Check HP-UX version
    Run 'uname -a' or 'swlist -l product' to identify the HP-UX version number
    Affected if Version is 9.00 or 10.00 specifically
  2. Locate cstm binary
    Run 'which cstm' or 'find / -name cstm -type f 2>/dev/null' to find the cstm binary
    Affected if cstm binary exists on the system
  3. Verify cstm binary permissions
    Run 'ls -la /usr/sbin/cstm' (or the full path found above) to check file permissions and ownership
    Affected if Binary is owned by root and has setuid bit set (rwsr-xr-x)
  4. Check if cstm is accessible to unprivileged users
    Run 'ls -la /usr/sbin/cstm' and verify other users have execute permission
    Affected if Non-root users have execute access to the cstm binary

User is affected if running HP-UX 9.00 or 10.00 with the cstm binary present, owned by root with setuid permissions, and accessible to unprivileged 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 patch for cstm or upgrade to a patched HP-UX version; restrict cstm binary permissions to authorized administrators only as an interim control.

Fix this in Hp Ux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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