dbcve.org
Database 10gDatabase / datastore · Oracle

CVE-2009-0976

MEDIUM · 5.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 →
61/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 10.2.0.4 and 11.1.0.6 allows remote authenticated users to affect confidentiality and integrity, related to LTADM.

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

Unspecified vulnerability in Oracle Database Workspace Manager component (related to LTADM) in versions 10.2.0.4 and 11.1.0.6 allows remote authenticated users to impact confidentiality and integrity. The CVSS 5.5 indicates the vulnerability is exploitable over the network with low attack complexity but requires authentication.

MitigationApply Oracle Critical Patch Updates (CPU) for the affected versions. Since the vulnerability requires authentication, also enforce least-privilege principles for database user accounts.

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.2.0.4
Database 11gDatabase / datastore
Affected:= 11.1.0.6

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
None

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

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 SYSDBA and run: SELECT * FROM v$version; OR check the ORATAB file /etc/oratab on Unix systems; OR run 'sqlplus / as sysdba' then 'SELECT VERSION FROM PRODUCT_COMPONENT_VERSION WHERE PRODUCT LIKE 'Oracle Database%';'
    Affected if The version displayed is exactly 10.2.0.4 or exactly 11.1.0.6 (these are the only affected versions per this CVE)
  2. Verify Workspace Manager component is installed
    Run SQL query: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Workspace%';
    Affected if Workspace Manager shows as INSTALLED in the STATUS column - the vulnerability exists in this component
  3. Confirm LTADM package exists in the database
    Run SQL query: SELECT OWNER, OBJECT_NAME, OBJECT_TYPE FROM DBA_OBJECTS WHERE OBJECT_NAME = 'LTADM' AND OBJECT_TYPE = 'PACKAGE';
    Affected if The LTADM package exists in the database - this is the specific vulnerable component mentioned in the CVE
  4. Check if database is network accessible
    Review the Oracle TNS Listener configuration using lsnrctl status; check sqlnet.ora for authentication parameters; verify the database accepts remote connections by testing connectivity from a remote host using tnsping or SQL*Net
    Affected if The database listener is active and accepting remote connections - the CVE notes exploitation is possible over the network for remote authenticated users
  5. Verify database user privileges exist
    Query DBA_ROLE_PRIVS and DBA_TAB_PRIVS to identify users with elevated privileges, particularly those related to Workspace Manager: SELECT GRANTEE, PRIVILEGE FROM DBA_TAB_PRIVS WHERE TABLE_NAME = 'LTADM';
    Affected if There are database users with privileges to execute LTADM operations - the vulnerability allows impact to confidentiality and integrity for authenticated users with appropriate access

Your environment is affected only if you are running exactly Oracle Database 10.2.0.4 or exactly 11.1.0.6 AND the Workspace Manager component with the LTADM package is installed AND the database accepts remote authenticated connections.

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 Updates (CPU) for the affected versions. Since the vulnerability requires authentication, also enforce least-privilege principles for database user accounts.

Fix this in Database 10g Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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