CVE-2009-0980
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 SQLX Functions component in Oracle Database 10.2.0.3 and 11.1.0.6 allows remote authenticated users to affect integrity and availability, related to AGGXQIMP.
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 · high confidenceUnspecified vulnerability in Oracle Database's SQLX Functions component (related to AGGXQIMP) affecting versions 10.2.0.3 and 11.1.0.6. Allows remote authenticated users to impact integrity and availability through malformed SQLX queries.
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.3= 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
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:N/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 Oracle Database versionConnect to the database as a privileged user (e.g., SYS or SYSTEM) and run: SELECT * FROM v$version; or SELECT version FROM product_component_version WHERE product LIKE 'Oracle Database%';Affected if The displayed version matches exactly 10.2.0.3 or 11.1.0.6
-
Confirm SQLX function usageQuery the library cache to find executed SQLX-related statements: SELECT sql_text FROM v$sqlarea WHERE sql_text LIKE '%XML%' OR sql_text LIKE '%SQLX%'; Review application code for usage of SQLX functions such as XMLAGG, XMLElement, XMLForest, XMLSequence, or other XML-related functions.Affected if SQLX or XML-generating functions are being used in the database workload
-
Verify remote listener accessCheck the Oracle listener configuration by running: lsnrctl status LISTENER; Review the LOCAL_LISTENER and REMOTE_LISTENER parameters: SELECT name, value FROM v$parameter WHERE name LIKE '%listener%'; Check sqlnet.ora for authentication protocol restrictions.Affected if The database listener is accessible from network hosts and REMOTE_LOGIN_PASSFILE is set to EXCLUSIVE or SHARING (allowing remote authentication)
-
Check for authenticated database users with network accessReview which database users have privileges to execute SQLX queries and are accessible remotely: SELECT username, profile, default_tablespace FROM dba_users WHERE account_status = 'OPEN'; Check for users with CONNECT role or custom roles enabling SQL execution.Affected if Any database user with execute privileges on SQLX-related packages (such as DBMS_XMLGEN, DBMS_XMLQUERY) can authenticate remotely to the database
The environment is affected if the Oracle Database version is exactly 10.2.0.3 or 11.1.0.6, SQLX functions are in use, and the database accepts remote authenticated connections.
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 upgrade to a patched version beyond 11.1.0.6. Restrict network access to database listeners and enforce least privilege for database accounts.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0980 — 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-0980 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