dbcve.org
SolarisOperating system · Sun

CVE-2000-0316

HIGH · 7.2 CVSS v2.0 Published 2000-04-24
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 Solaris 7 lp allows local users to gain root privileges via a long -d option.

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

A buffer overflow vulnerability exists in the lp (line printer) daemon/service in Solaris 7. The vulnerability is triggered when a local user provides an excessively long argument to the -d option (which specifies the print queue or destination). This overflow allows local attackers to execute arbitrary code with root privileges, achieving privilege escalation from a standard user account to full system control.

MitigationApply the appropriate Solaris patch for the lp vulnerability (contact Oracle for legacy patches), or upgrade from the obsolete Solaris 7 to a supported version. Alternatively, restrict or disable local access to the lp command and printer subsystem for 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
SolarisOperating system
Affected:= 7.0
SunosOperating system
Affected:= 5.7

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 version
    Run `uname -a` or check `/etc/release` to determine the exact Solaris version
    Affected if The system is running SunOS 5.7 or Solaris 7.0 specifically
  2. Locate the lp binary
    Check for the existence of the lp command using `which lp` or `ls -la /usr/bin/lp`
    Affected if The lp binary exists on the system in standard locations
  3. Verify lp binary permissions
    Run `ls -la /usr/bin/lp` to check owner, group, and permission bits
    Affected if The lp binary is executable by standard users (world-executable or group-executable for users other than root)
  4. Confirm printer subsystem accessibility
    Test if a non-root user can invoke the lp command by running `lp -d` with a test queue name
    Affected if Non-privileged users can execute the lp command and access the printer subsystem

A system is affected if it runs Solaris 7.0 (SunOS 5.7) and allows non-root users to access the lp command with the -d option, enabling local privilege escalation.

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 the appropriate Solaris patch for the lp vulnerability (contact Oracle for legacy patches), or upgrade from the obsolete Solaris 7 to a supported version. Alternatively, restrict or disable local access to the lp command and printer subsystem for untrusted users.

Fix this in Solaris 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-2000-0316 — 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-2000-0316 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