JetadminApplication · Hp

CVE-1999-1433

HIGH · 7.2 CVSS v2.0 Published 1998-07-15
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
HP JetAdmin D.01.09 on Solaris allows local users to change the permissions of arbitrary files via a symlink attack on the /tmp/jetadmin.log file.

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

HP JetAdmin D.01.09 on Solaris is vulnerable to a symlink attack via /tmp/jetadmin.log. A local user can create a symbolic link from /tmp/jetadmin.log to an arbitrary target file before the application runs. When JetAdmin executes (with elevated privileges), it follows the symlink and changes permissions on the target file, potentially allowing privilege escalation.

MitigationUpgrade HP JetAdmin to a patched version if available, or implement filesystem-level controls such as mounting /tmp with nosuid,noexec options and ensuring strict file permissions to prevent symlink creation in /tmp by untrusted 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
JetadminApplication
Affected:= rev._d.01.09

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. Determine if HP JetAdmin is installed
    Locate the JetAdmin binary. Common paths on Solaris include /opt/hp/jetadmin/ or check with 'which hpnp' or 'ls -la /opt' for hp-related directories. Also check 'pkginfo | grep -i jet' if available.
    Affected if HP JetAdmin binary is found on the system
  2. Check the installed JetAdmin version
    Run the JetAdmin binary with version flags such as 'hpnp -V', 'hpnpadmin -V', or check the binary directly with 'strings' or 'what' command. The affected version is D.01.09.
    Affected if The installed version is exactly D.01.09 (rev._d.01.09)
  3. Verify if /tmp/jetadmin.log exists and is a symlink
    Run 'ls -la /tmp/jetadmin.log' to check if the file exists and whether it is a symbolic link. Also check 'file /tmp/jetadmin.log' to confirm the file type.
    Affected if The file /tmp/jetadmin.log exists as a symbolic link pointing to an unintended target, or has unusual ownership/permissions indicating exploitation
  4. Check ownership and permissions of /tmp directory
    Run 'ls -lad /tmp' to verify /tmp has restricted permissions (typically 1777 with sticky bit). Check if untrusted users can create files in /tmp.
    Affected if The /tmp directory allows untrusted users to create symlinks (permissions are overly permissive or sticky bit is missing)
  5. Identify if JetAdmin runs with elevated privileges
    Check the permissions of the JetAdmin binary with 'ls -la <path_to_jetadmin>' and check if it has setuid/setgid bits. Also examine /etc/permissions or similar privilege assignment files on Solaris.
    Affected if JetAdmin runs with root or elevated privileges (has setuid bit set or runs as root user)

A system is affected if HP JetAdmin version D.01.09 is installed, runs with elevated privileges, and the /tmp directory permits untrusted users to create symlinks, allowing a symlink at /tmp/jetadmin.log to be exploited.

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

Upgrade HP JetAdmin to a patched version if available, or implement filesystem-level controls such as mounting /tmp with nosuid,noexec options and ensuring strict file permissions to prevent symlink creation in /tmp by untrusted users.

Fix this in Jetadmin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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