dbcve.org
UnixOperating system · Digital

CVE-2001-0369

HIGH · 7.2 CVSS v2.0 Published 2001-06-27
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 lpsched on DGUX version R4.20MU06 and MU02 allows a local attacker to obtain root access via a long command line argument (non-existent printer name).

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 in the lpsched (line printer scheduler) daemon on DGUX R4.20MU06 and MU02 allows a local attacker to execute arbitrary code with root privileges by passing an excessively long command line argument, specifically a non-existent printer name.

MitigationRestrict local access to the lpsched binary, apply any vendor-supplied patches for DGUX R4.20, or consider upgrading/replacing the legacy DGUX system if vendor support is unavailable.

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
UnixOperating system
Affected:= mu02= r4.20mu06

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
    Run 'uname -a' or 'uname -sr' to confirm the system is DGUX
    Affected if The OS is not DGUX or the output does not show DGUX as the operating system
  2. Check the DGUX version
    Examine /etc/version, /etc/uxrelease, or run 'osinfo -v' to identify the exact DGUX release level
    Affected if The version is r4.20mu06 or r4.20mu02 exactly, or falls within the r4.20 mu02 through mu06 range without patches applied
  3. Locate the lpsched binary
    Check for the lpsched binary using 'which lpsched' or 'find /usr -name lpsched -type f'
    Affected if The lpsched binary exists on the system, indicating the vulnerable component is present
  4. Verify lpsched is executable
    Run 'ls -la /usr/lib/lpsched' or the appropriate path from the previous step to check file permissions
    Affected if The lpsched binary has execute permissions, meaning it can be invoked and the vulnerability is reachable

A system is affected if it runs DGUX version r4.20mu02 or r4.20mu06, has the lpsched binary present and executable, and the vulnerability is exploitable locally via a long printer name argument to lpsched.

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 local access to the lpsched binary, apply any vendor-supplied patches for DGUX R4.20, or consider upgrading/replacing the legacy DGUX system if vendor support is unavailable.

Fix this in Unix Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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