dbcve.org
Application ServerApplication · Oracle

CVE-2006-0286

HIGH · 10.0 CVSS v2.0 Published 2006-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Unspecified vulnerability in the Oracle HTTP Server component of Oracle Database Server 9.0.1.5, 9.0.1.5 FIPS, 9.2.0.7, and 10.1.0.5, and Application Server 1.0.2.2, 9.0.4.2, and 10.1.2.0.2, has unspecified impact and attack vectors, as identified by Oracle Vuln# OHS01.

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

CVE-2006-0286 is a critical severity (CVSS 10) unspecified vulnerability in the Oracle HTTP Server component affecting very old Oracle Database Server versions (9.0.1.5 through 10.1.0.5) and Application Server versions (1.0.2.2 through 10.1.2.0.2). The exact attack vector and technical details are not disclosed in Oracle's vulnerability documentation, which is typical for Oracle Critical Patch Updates to prevent immediate exploitation.

MitigationApply Oracle Critical Patch Update (CPU) for January 2006; however, these affected versions are long-end-of-life and require upgrade to supported Oracle releases. If patching is impossible, implement strict network segmentation and disable the Oracle HTTP Server if not required.

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
Application ServerApplication
Affected:= 1.0.2.2= 9.0.4.2= 10.1.2.0.2
Database ServerDatabase / datastore
Affected:= 9.0.1.5= 9.2.0.7= 10.1.0.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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/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 Oracle product installation
    Determine if Oracle Database Server or Oracle Application Server is installed. Check for Oracle installation directories such as $ORACLE_HOME or /opt/oracle. On Windows, check Services for Oracle-related services.
    Affected if Oracle Database Server or Oracle Application Server is present on the system
  2. Locate Oracle HTTP Server component
    Identify the Oracle HTTP Server binary or service. On Unix systems, check for Apachectl or httpd in Oracle home directories under $ORACLE_HOME/Apache/Apache/bin. On Windows, look for Oracle HTTP Server service.
    Affected if Oracle HTTP Server component exists in the Oracle installation
  3. Determine Oracle HTTP Server version
    Run the HTTP Server version command. For Apache-based installations, execute: $ORACLE_HOME/Apache/Apache/bin/httpd -v or check the version string in the httpd binary. Alternatively, check the Oracle inventory file or patch inventory for the version.
    Affected if The Oracle HTTP Server version matches 9.0.1.5, 9.2.0.7, 10.1.0.5, 1.0.2.2, 9.0.4.2, or 10.1.2.0.2
  4. Confirm Oracle product version matches affected ranges
    Run: sqlplus /v (for Database Server) or check Oracle Application Server version via opmnctl status. Compare the Oracle Database version (select version from v$instance) or Application Server version against the affected ranges.
    Affected if Oracle Database Server version is 9.0.1.5, 9.2.0.7, or 10.1.0.5, OR Oracle Application Server version is 1.0.2.2, 9.0.4.2, or 10.1.2.0.2

If Oracle HTTP Server component is present and its version matches any of the affected versions (9.0.1.5, 9.2.0.7, 10.1.0.5, 1.0.2.2, 9.0.4.2, or 10.1.2.0.2), the environment is vulnerable to CVE-2006-0286.

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 Oracle Critical Patch Update (CPU) for January 2006; however, these affected versions are long-end-of-life and require upgrade to supported Oracle releases. If patching is impossible, implement strict network segmentation and disable the Oracle HTTP Server if not required.

Fix this in Application Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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