CVE-2009-0975
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 · uneditedUnspecified 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 via unknown vectors, a different vulnerability than CVE-2009-0978.
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 confidenceUnspecified vulnerability in Oracle Database Workspace Manager component (versions 10.2.0.4 and 11.1.0.6) allows remote authenticated users to impact confidentiality and integrity through unknown vectors. This is a data-level access control issue in the Workspace Manager feature that manages collaborative workspaces within the database.
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= 10.2.0.4= 11.1.0.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Oracle Database versionQuery SELECT VERSION FROM V$INSTANCE; or check the Oracle inventory for the installed database version.Affected if The installed version is exactly 10.2.0.4 or exactly 11.1.0.6 (these are the specific affected versions)
-
Confirm Workspace Manager component is installedQuery SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE 'Workspace Manager'; or check if the WM$ADMIN_TABLE package exists.Affected if Workspace Manager is installed and present in the database registry with status VALID
-
Verify if workspaces exist in the databaseQuery SELECT OWNER, WORKSPACE_NAME FROM DBA_WORKSPACES; or connect as a user with privileges to query the Workspace Manager metadata.Affected if Any workspaces are configured and active in the database
-
Check for granted privileges on Workspace Manager objectsQuery SELECT GRANTEE, OWNER, TABLE_NAME FROM DBA_TAB_PRIVS WHERE OWNER = 'WM' AND GRANTEE NOT IN ('WM', 'SYS', 'SYSTEM');Affected if Additional users or roles have been granted privileges on Workspace Manager objects beyond the default owners
A user is affected if they run Oracle Database version 10.2.0.4 or 11.1.0.6 AND the Workspace Manager component is installed with active workspaces.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update April 2009 or later, which contains the fix for this vulnerability. For unsupported versions, upgrade to a currently supported Oracle Database release that includes security patches.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0975 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-0975 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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