dbcve.org
Database 10gDatabase / datastore · Oracle

CVE-2009-0973

MEDIUM · 5.0 CVSS v2.0 Published 2009-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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 Cluster Ready Services component in Oracle Database 10.1.0.5 allows remote attackers to affect availability via unknown vectors.

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

Vulnerability in Oracle Database 10.1.0.5 Cluster Ready Services (CRS) component allows remote attackers to impact system availability through unspecified vectors. The vulnerability is exploitable remotely with low complexity, though the exact attack method is not disclosed in Oracle's advisory.

MitigationApply Oracle Critical Patch Update (CPU) for April 2009 or later, or upgrade to a supported Oracle Database version as 10.1.0.5 is well beyond extended support.

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
Database 10gDatabase / datastore
Affected:= 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
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/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 Oracle Database installation
    Query the Oracle inventory directory (typically /etc/oraInst.loc on Linux/Unix or registry on Windows) or check for ORACLE_HOME environment variable
    Affected if No Oracle Database installation is found or ORACLE_HOME is not set
  2. Confirm the exact Oracle Database version
    Run: sqlplus / as sysdba, then execute SELECT VERSION FROM PRODUCT_COMPONENT_VERSION WHERE PRODUCT LIKE 'Oracle%'; or check $ORACLE_HOME/oracle/orapw file version, or check opatch lsinventory
    Affected if The installed version is exactly 10.1.0.5 (not 10.1.0.4, 10.2.x, or later)
  3. Check if Cluster Ready Services (CRS) component is installed
    On Linux/Unix systems, check if the CRS home exists under /opt/oracle/crs or /u01/app/oracle/product/10.1.0/crs, or run: crsctl query crs activeversion 2>/dev/null
    Affected if CRS is installed and the CRS home directory exists on the system (vulnerability only applies if CRS is present)
  4. Verify CRS version
    Run: $CRS_HOME/bin/crsctl query crs activeversion or check the CRS inventory file
    Affected if CRS version reports 10.1.0.5 (indicating the exact vulnerable version)

A user is affected if they have Oracle Database 10g version 10.1.0.5 with the Cluster Ready Services (CRS) component installed and active.

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 April 2009 or later, or upgrade to a supported Oracle Database version as 10.1.0.5 is well beyond extended support.

Fix this in Database 10g Scoped from the published advisory
  • Consultation16.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA8.0 h
88.0 hours of engineering $15,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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