dbcve.org
Web Based Enterprise ManagementApplication · Sun

CVE-1999-0982

HIGH · 7.2 CVSS v2.0 Published 1999-12-05
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
The Sun Web-Based Enterprise Management (WBEM) installation script stores a password in plaintext in a world readable 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

The Sun WBEM installation script creates a file containing a plaintext password with world-readable permissions, allowing any local user to obtain the credentials.

MitigationRemove or secure the file containing plaintext credentials and rotate the exposed password immediately.

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
Web Based Enterprise ManagementApplication
Affected:= 1.0= 2.0
SolarisOperating system
Affected:= 8.0

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 Sun WBEM is installed
    Run command to list installed WBEM packages or check common installation directories for WBEM software
    Affected if Sun Web Based Enterprise Management versions 1.0 or 2.0 are installed on Sun Solaris 8.0 or related systems
  2. Locate the WBEM credential file
    Search the WBEM installation directory for files that may contain stored credentials or password data - examine files created during or after installation
    Affected if A file containing plaintext credentials exists in the WBEM installation path
  3. Inspect file permissions on the credential file
    Use 'ls -la' or similar command to view the permissions on the identified credential file
    Affected if The file permissions show 'world-readable' access (typically shown as 'r--r--r--' or similar with 'other' read bits set)
  4. Verify any local user can read the credentials
    As a non-privileged test user, attempt to read the credential file using standard file read commands
    Affected if A local unprivileged user can successfully read the file contents containing plaintext passwords

The environment is affected if Sun WBEM 1.0 or 2.0 is installed on Solaris 8.0 and a file containing plaintext credentials exists with world-readable permissions allowing any local user to access the password

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

Remove or secure the file containing plaintext credentials and rotate the exposed password immediately.

Fix this in Web Based Enterprise Management Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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