dbcve.org
Hp UxOperating system · Hp

CVE-2004-2693

HIGH · 7.2 CVSS v2.0 Published 2004-12-31
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-UX B.11.00 and B.11.11 with B6848AB GTK+ Support Libraries installed uses insecure directory permissions, which allows local users to gain privileges via files in /opt/gnome/src/GLib/.

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

Local privilege escalation vulnerability in HP-UX B.11.00 and B.11.11 with B6848AB GTK+ Support Libraries. The /opt/gnome/src/GLib/ directory has insecure permissions allowing any local user to create or modify files, which can be leveraged to gain elevated privileges through executable injection or library hijacking.

MitigationRestrict permissions on /opt/gnome/src/GLib/ to prevent write access by unprivileged users (remove world/group write permissions, ensure only root owns the directory). Audit similar GNOME/GTK+ directories for identical permission issues.

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:= 11.00= 11.04= 11.11

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. Confirm HP-UX version
    Run 'uname -a' or 'swlist -l bundle' to identify the HP-UX release (B.11.00 or B.11.11)
    Affected if The system is running HP-UX B.11.00 or B.11.11
  2. Check if GTK+ Support Libraries are installed
    Run 'swlist -l product | grep -i gtk' or 'swlist -l product B6848AB' to see if the B6848AB GTK+ Support Libraries are present
    Affected if The B6848AB GTK+ Support Libraries package is installed on the system
  3. Verify /opt/gnome/src/GLib/ directory exists
    Run 'ls -ld /opt/gnome/src/GLib/' to check if the directory exists
    Affected if The directory /opt/gnome/src/GLib/ exists on the system
  4. Inspect permissions on the GLib directory
    Run 'ls -ld /opt/gnome/src/GLib/' and examine the permission bits (owner, group, world write permissions)
    Affected if The directory is owned by a non-root user OR has world-writable (o+w) or group-writable (g+w) permissions set
  5. Check for similar GNOME directory permission issues
    Run 'ls -ld /opt/gnome/src/*/' to list permissions on related GNOME directories under /opt/gnome/src/
    Affected if Other GNOME directories under /opt/gnome/src/ have insecure permissions (world-writable or non-root ownership)

The system is affected if it is HP-UX B.11.00 or B.11.11 with B6848AB GTK+ Support Libraries installed and /opt/gnome/src/GLib/ exists with insecure (world-writable or non-root owned) permissions.

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

Restrict permissions on /opt/gnome/src/GLib/ to prevent write access by unprivileged users (remove world/group write permissions, ensure only root owns the directory). Audit similar GNOME/GTK+ directories for identical permission issues.

Fix this in Hp Ux Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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