CVE-2009-0986
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, 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 · moderate confidenceThis is an Oracle Database vulnerability in the Workspace Manager component affecting versions 10.2.0.4 and 11.1.0.6. The vulnerability allows remote authenticated users to impact confidentiality, integrity, and availability through unknown vectors, rated CVSS 5.4 (MEDIUM).
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
- M
- Authentication
- Multiple
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:M/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Oracle Database versionConnect to the database as a privileged user (e.g., SYS or SYSTEM) and query V$VERSION or SELECT BANNER FROM V$VERSION; alternatively, query PRODUCT_COMPONENT_VERSION from PRODUCT_COMPONENT_VERSIONAffected if The displayed version is exactly 10.2.0.4 (Oracle Database 10g) or exactly 11.1.0.6 (Oracle Database 11g)
-
Confirm the Workspace Manager component is installedQuery the DBA_REGISTRY view: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Workspace Manager%';Affected if Workspace Manager appears in the results with a status of VALID or LOADED (indicating the component is installed)
-
Verify if Workspace Manager is actually in useQuery the DBA_WORKSPACES view (accessible to DBA users): SELECT WORKSPACE_NAME, CREATION_DATE FROM DBA_WORKSPACES; or check for active workspace objects in the databaseAffected if Any workspaces exist in the database (the vulnerability requires Workspace Manager to be present and accessible)
-
Check for public privileges on Workspace Manager objectsQuery DBA_TAB_PRIVS for privileges granted on WMSYS schema objects: SELECT GRANTEE, TABLE_NAME, PRIVILEGE FROM DBA_TAB_PRIVS WHERE OWNER = 'WMSYS';Affected if Users other than SYS or WMSYS have privileges on Workspace Manager objects, indicating potential attack surface
You are affected if your Oracle Database is exactly version 10.2.0.4 or 11.1.0.6 AND the Workspace Manager component is installed and accessible in the database.
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 the relevant Oracle Critical Patch Update (CPU) for April 2009 or later that addresses this Workspace Manager vulnerability. Prior to patching, backup the database and test in a non-production environment to ensure compatibility.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2009-0986 — 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-0986 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