dbcve.org
LinuxOperating system · Redhat

CVE-2000-0357

HIGH · 7.5 CVSS v2.0 Published 1999-12-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
ORBit and esound in Red Hat Linux 6.1 do not use sufficiently random numbers, which allows local users to guess the authentication keys.

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

ORBit and esound in Red Hat Linux 6.1 use insufficiently random numbers for authentication key generation, allowing local users to brute-force or guess the keys and potentially gain unauthorized access to these services.

MitigationThis is a legacy vulnerability in Red Hat Linux 6.1 (circa 2000). Modern systems are not affected. For any remaining legacy deployments, upgrade to supported software versions and ensure cryptographic random number generation is used for authentication keys.

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

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
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 installed operating system version
    Run 'cat /etc/redhat-release' or 'cat /etc/issue' to check the OS version
    Affected if The system is not Red Hat Linux 6.1 (modern systems are not affected)
  2. Check if ORBit is installed
    Run 'rpm -q ORBit' or 'rpm -qa | grep -i orbit' to query the RPM package database
    Affected if ORBit package is installed on Red Hat Linux 6.1 and the service is in use
  3. Check if esound is installed
    Run 'rpm -q esound' or 'rpm -qa | grep -i esound' to query the RPM package database
    Affected if esound package is installed on Red Hat Linux 6.1 and the service is in use
  4. Determine if affected services are running
    Run 'ps aux | grep -E "(orbit|esd)"' to check if ORBit or esound daemons are active
    Affected if ORBit or esound services are running on a vulnerable Red Hat Linux 6.1 system

A user is affected only if running Red Hat Linux 6.1 with ORBit or esound packages installed and services enabled, as the vulnerability requires these specific packages on this exact OS version to be exploitable.

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

This is a legacy vulnerability in Red Hat Linux 6.1 (circa 2000). Modern systems are not affected. For any remaining legacy deployments, upgrade to supported software versions and ensure cryptographic random number generation is used for authentication keys.

Fix this in Linux 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-0357 — 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-0357 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