CVE-2009-0987
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 Upgrade component in Oracle Database 9.2.0.8, 9.2.0.8DV, 10.1.0.5, and 10.2.0.3 allows remote authenticated users to affect confidentiality and integrity 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 confidenceA remote authenticated vulnerability in the Oracle Database Upgrade component allows attackers to potentially read or modify data through unspecified vectors. The vulnerability affects Oracle 9i and 10g versions (9.2.0.8, 9.2.0.8DV, 10.1.0.5, 10.2.0.3) and requires valid database credentials for exploitation.
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= 9.2.0.8= 9.2.0.8dv= 10.1.0.5= 10.2.0.3CVSS 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.
-
Identify Oracle Database versionConnect to the database as a privileged user and run: SELECT VERSION FROM PRODUCT_COMPONENT_VERSION WHERE PRODUCT LIKE 'Oracle%'; or check the oratab file /etc/oratab on the database server for the Oracle home entry.Affected if The version shown is exactly 9.2.0.8, 9.2.0.8dv, 10.1.0.5, or 10.2.0.3
-
Confirm the Upgrade component is presentQuery the DBA_REGISTRY or V$OPTION view to check for the presence of the Upgrade component: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Upgrade%';Affected if The Upgrade component is installed and accessible in the affected version
-
Verify network listener accessibilityCheck if the Oracle Listener is running and accessible remotely: lsnrctl status LISTENER (from the server) or attempt a remote connection to the database port (default 1521) from an external host.Affected if The database is reachable over the network and remote connections are permitted by the listener configuration
-
Review database user authenticationDetermine if any valid database user accounts exist that could be leveraged: SELECT USERNAME FROM DBA_USERS WHERE ACCOUNT_STATUS = 'OPEN';Affected if The database has any enabled user accounts that could provide the credentials required for exploitation
The environment is affected only if the Oracle Database version matches exactly 9.2.0.8, 9.2.0.8dv, 10.1.0.5, or 10.2.0.3 AND the Upgrade component is present and accessible with valid credentials.
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 corresponding Oracle Critical Patch Update (CPU) from April 2009 that addresses this vulnerability, or upgrade to a supported Oracle Database version if these end-of-life releases cannot be patched.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0987 — 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-0987 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