dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2009-0972

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 Workspace Manager component in Oracle Database 11.1.0.6, 11.1.0.7, 10.2.0.3, 10.2.0.4, 10.1.0.5, 9.2.0.8, and 9.2.0.8DV allows remote authenticated users to affect confidentiality, integrity, and 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 · low confidence

Unspecified vulnerability in Oracle Workspace Manager component allows remote authenticated users to affect confidentiality, integrity, and availability via unknown vectors. This affects Oracle Database versions 9.2.0.8, 9.2.0.8DV, 10.1.0.5, 10.2.0.3, 10.2.0.4, 11.1.0.6, and 11.1.0.7.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for April 2009, or upgrade to a supported Oracle Database version. If patching is not feasible, restrict network access to database listeners and limit privileges for Workspace Manager users.

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 ServerDatabase / datastore
Affected:= 9.2.0.8= 9.2.0.8dv= 10.1.0.5= 10.2.0.3= 10.2.0.4= 11.1.0.6= 11.1.0.7

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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/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 Oracle Database version
    Connect to the database as a privileged user (e.g., SYS or SYSTEM) and run: SELECT VERSION FROM V$INSTANCE; or SELECT BANNER FROM V$VERSION;
    Affected if The version matches one of the following: 9.2.0.8, 9.2.0.8DV, 10.1.0.5, 10.2.0.3, 10.2.0.4, 11.1.0.6, or 11.1.0.7
  2. Confirm Workspace Manager component is installed
    Query the DBA_REGISTRY view: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Workspace%';
    Affected if Workspace Manager appears in the registry with status VALID or any status, indicating the component is present
  3. Check if Workspace Manager is actively in use
    Query user tables that may be owned by the Workspace Manager schema (OWM), or check for objects owned by the WMSYS user: SELECT OWNER, COUNT(*) FROM DBA_OBJECTS WHERE OWNER='WMSYS' GROUP BY OWNER;
    Affected if Objects owned by WMSYS exist, indicating Workspace Manager has been used or configured in the database
  4. Assess network exposure of the database listener
    Review the LISTENER.ORA file for configured listeners, and use the command: lsnrctl status LISTENER (or the configured listener name) to see current listener endpoints and IP bindings; check if the listener is bound to non-localhost addresses.
    Affected if The database listener is bound to a network-accessible IP address (0.0.0.0 or a specific hostname/IP) rather than only localhost (127.0.0.1)
  5. Verify remote authentication is possible
    Check for database users with remote authentication enabled: SELECT USERNAME, AUTHENTICATION_TYPE FROM DBA_USERS WHERE AUTHENTICATION_TYPE LIKE '%EXTERNAL%' OR AUTHENTICATION_TYPE LIKE '%GLOBAL%'; Also check if the database accepts connections from non-local hosts.
    Affected if External or global authenticated users exist, or the database is accessible from remote hosts without VPN or firewall restrictions

You are affected if your Oracle Database version is one of the listed affected versions AND Workspace Manager is installed AND the database is network-accessible to remote authenticated users.

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 the relevant Oracle Critical Patch Update (CPU) for April 2009, or upgrade to a supported Oracle Database version. If patching is not feasible, restrict network access to database listeners and limit privileges for Workspace Manager users.

Fix this in Database Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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