dbcve.org
Oracle8iDatabase / datastore · Oracle

CVE-2000-0206

MEDIUM · 6.2 CVSS v2.0 Published 2000-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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 installation of Oracle 8.1.5.x on Linux follows symlinks and creates the orainstRoot.sh file with world-writeable permissions, which allows local users to gain 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 · high confidence

The Oracle 8.1.5.x installer on Linux creates the orainstRoot.sh script with world-writeable permissions and follows symlinks during installation. A local attacker can either replace this script with malicious content or exploit symlink attacks to execute arbitrary code with root privileges.

MitigationChange orainstRoot.sh permissions to 0700 or 0755 (root-only writable) and ensure the Oracle installation does not follow symlinks in sensitive paths. Verify file ownership is root:oracle.

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
Oracle8iDatabase / datastore
Affected:= 8.1.5

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
High
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:H/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. Locate the Oracle 8.1.5 installation
    Check for Oracle inventory file at /etc/oraInst.loc or search for 'orainstRoot.sh' using: find / -name 'orainstRoot.sh' 2>/dev/null
    Affected if Oracle 8.1.5 is installed and the orainstRoot.sh script exists on the system
  2. Verify Oracle version is 8.1.5.x
    Check the Oracle inventory or run: strings $ORACLE_HOME/bin/oracle | grep '8.1.5' (replace $ORACLE_HOME with your Oracle home path)
    Affected if The installed Oracle version is 8.1.5 (any subversion)
  3. Check orainstRoot.sh permissions
    Run: ls -la /path/to/orainstRoot.sh (use path found in step 1) and check the permission bits
    Affected if The file permissions show 'w' for 'other' users (e.g., mode ends with 6 or 7, such as 0666 or 0777)
  4. Verify orainstRoot.sh ownership
    Run: ls -la /path/to/orainstRoot.sh and check the owner/group columns
    Affected if The file is not owned by root or is owned by oracle without root-only write permissions

If Oracle 8.1.5 is installed and the orainstRoot.sh file exists with world-writeable permissions (writable by 'other' users), the system is vulnerable to local privilege escalation via this script replacement or symlink attack.

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

Change orainstRoot.sh permissions to 0700 or 0755 (root-only writable) and ensure the Oracle installation does not follow symlinks in sensitive paths. Verify file ownership is root:oracle.

Fix this in Oracle8i Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
4.5 hours of engineering $820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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