CVE-2009-0979
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 Resource Manager component in Oracle Database 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 · moderate confidenceCVE-2009-0979 is an unspecified vulnerability in the Resource Manager component of Oracle Database 9.2.0.8 and 9.2.0.8DV. Remote authenticated users can exploit unknown vectors to impact confidentiality, integrity, and availability. The Resource Manager controls database resource allocation between sessions and operations.
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.8dvCVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:S/C:C/I:C/A:C
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.
-
Determine Oracle Database versionConnect 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 WHERE BANNER LIKE 'Oracle Database%';Affected if The version output shows 9.2.0.8 or 9.2.0.8dv exactly, indicating the vulnerable release is installed.
-
Confirm Resource Manager component statusQuery the Resource Manager metadata to confirm the component exists: SELECT COMPONENT, STATUS FROM DBA_REGISTRY WHERE COMPONENT LIKE '%Resource Manager%'; or check if resource plans are defined with SELECT PLAN, STATUS FROM DBA_RSRC_PLANS;Affected if The Resource Manager component is present (this is default in 9i) - all 9.2.0.8 and 9.2.0.8dv installations with Resource Manager enabled are affected.
-
Verify if any resource plans are activeCheck for active resource plans by running: SELECT NAME, IS_TOP_PLAN FROM V$RSRC_PLAN; or SELECT PLAN, STATUS FROM DBA_RSRC_PLANS WHERE STATUS = 'ACTIVE';Affected if An active resource plan exists - exploitation requires authenticated access to the database, typically via a database session.
-
Review audit logs for suspicious Resource Manager activityExamine Oracle audit trail for unusual Resource Manager operations: SELECT TIMESTAMP#, ACTION_NAME, OBJ_NAME, USERID FROM DBA_AUDIT_TRAIL WHERE ACTION_NAME LIKE '%RESOURCE%' OR OBJ_NAME LIKE '%RSRC%'; Check also for failed login attempts preceding any anomalous activity.Affected if Unusual or unauthorized resource plan modifications or executions are found in audit records, which may indicate exploitation attempts.
A system is affected if it runs Oracle Database 9.2.0.8 or 9.2.0.8dv with the Resource Manager component enabled, regardless of whether specific resource plans are configured.
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.
dbcve · scopedApply the relevant Oracle Critical Patch Update (CPU) for April 2009, or if Oracle 9i is no longer supported, migrate to a currently supported Oracle Database version. Verify all Resource Manager configurations post-patch.
Oracle 11g or 12c (supported versions)
- Apply Oracle Critical Patch Update (CPU) for April 2009 or later. Oracle releases CPUs quarterly, and this vulnerability (CVE-2009-0979) was addressed in the April 2009 CPU.
- Contact Oracle Support to obtain the specific patch for this vulnerability if not included in the quarterly CPU.
- If upgrading from Oracle 9i is feasible, consider migrating to a supported Oracle Database version (11g or later) as Oracle 9i reached end of support.
Generated from the published advisory — verify against the referenced sources before acting.
- 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-0979 — 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-0979 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