dbcve.org
Suse LinuxOperating system · Suse

CVE-2000-0362

HIGH · 7.2 CVSS v2.0 Published 1999-10-22
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 overflows in Linux cdwtools 093 and earlier allows local users to gain root privileges.

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

Buffer overflow vulnerabilities in cdwtools version 093 and earlier allow local authenticated users to execute arbitrary code with elevated root privileges. The vulnerability stems from insufficient bounds checking in the CD writing utility, enabling privilege escalation from a standard user account to full root access.

MitigationUpgrade cdwtools to a version beyond 093 that includes the security patch, or remove the software from systems if no longer needed, as this is legacy CD writing software from 2000.

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
Suse LinuxOperating system
Affected:= 6.1= 6.2

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. Check if cdwtools is installed
    Query the package manager for cdwtools using 'rpm -qa | grep -i cdwtools' or check for the binary at /usr/bin/cdwtools if it exists
    Affected if cdwtools package or binary is present on the system
  2. Determine the cdwtools version
    Run 'cdwtools -v' or 'rpm -q cdwtools' to retrieve the installed version number
    Affected if version is 0.93 or earlier, or version cannot be determined (assumed vulnerable)
  3. Identify the operating system version
    Check the Suse version using 'cat /etc/SuSE-release' or 'lsb_release -a'
    Affected if running Suse Linux 6.1 or 6.2
  4. Verify presence of local user accounts
    Check for non-root users with 'grep -E '^[^:]+:[^:]+:[0-9]+:' /etc/passwd' to list local accounts
    Affected if local authenticated users exist on the system who could potentially exploit the vulnerability

The system is affected if cdwtools version 0.93 or earlier is installed on Suse Linux 6.1 or 6.2 and local user accounts exist, as the buffer overflow can be exploited for privilege escalation to root.

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 cdwtools to a version beyond 093 that includes the security patch, or remove the software from systems if no longer needed, as this is legacy CD writing software from 2000.

Fix this in Suse Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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