CVE-2009-0977
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 Advanced Queuing 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, related to DBMS_AQIN. NOTE: the previous information was obtained from the April 2009 CPU. Oracle has not commented on reliable researcher claims that this issue is SQL injection in the GRANT_TYPE_ACCESS procedure in the DBMS_AQADM_SYS package.
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 confidenceSQL injection vulnerability in Oracle Database's Advanced Queuing component (DBMS_AQIN package, specifically in the GRANT_TYPE_ACCESS procedure of DBMS_AQADM_SYS). Allows remote authenticated users to execute arbitrary SQL statements, impacting confidentiality and integrity.
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.1.0.5= 10.2.0.3= 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
- 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 versionExecute: SELECT version FROM product_component_version; or SELECT * FROM v$version; to determine the exact installed version.Affected if Version matches 9.2.0.8, 9.2.0.8dv, 10.1.0.5, or 10.2.0.3
-
Verify DBMS_AQIN package existsExecute: SELECT owner, object_name, object_type FROM dba_objects WHERE object_name = 'DBMS_AQIN';Affected if The package exists and is valid in the database
-
Confirm GRANT_TYPE_ACCESS procedure existsExecute: SELECT owner, object_name, procedure_name FROM dba_procedures WHERE object_name = 'DBMS_AQADM_SYS' AND procedure_name = 'GRANT_TYPE_ACCESS';Affected if The GRANT_TYPE_ACCESS procedure exists in DBMS_AQADM_SYS package
-
Check if Advanced Queuing is in useExecute: SELECT owner, queue_name, subscriber_type FROM dba_queue_subscribers; or check for AQ agents with SELECT * FROM dba aq_subscribers;Affected if Any Advanced Queuing subscribers or agents are configured (indicates AQ is active)
-
Check execute privileges on vulnerable packageExecute: SELECT grantee, owner, table_name, privilege FROM dba_tab_privs WHERE table_name IN ('DBMS_AQIN', 'DBMS_AQADM_SYS');Affected if Non-privileged users have execute access to DBMS_AQIN or DBMS_AQADM_SYS packages
A user is affected if they run Oracle Database 9.2.0.8/9.2.0.8dv/10.1.0.5/10.2.0.3 AND the DBMS_AQIN/DBMS_AQADM_SYS package with GRANT_TYPE_ACCESS procedure is present and accessible in their environment.
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). If patching is not feasible, restrict network access to database and limit privileges of database accounts using Advanced Queuing.
- 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-0977 — 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-0977 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