dbcve.org
Oracle10gDatabase / datastore · Oracle

CVE-2006-0272

HIGH · 9.0 CVSS v2.0 Published 2006-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Unspecified vulnerability in the XML Database component of Oracle Database server 9.2.0.7 and 10.1.0.4 has unspecified impact and attack vectors, as identified by Oracle Vuln# DB29. NOTE: based on mutual credits by the relevant sources, it is highly likely that this issue is a buffer overflow in the (a) DBMS_XMLSCHEMA and (b) DBMS_XMLSCHEMA_INT packages, as exploitable via long arguments to (1) XDB.DBMS_XMLSCHEMA.GENERATESCHEMA or (2) XDB.DBMS_XMLSCHEMA.GENERATESCHEMAS.

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 confidence

Buffer overflow vulnerability in Oracle Database's XML Database component (DBMS_XMLSCHEMA and DBMS_XMLSCHEMA_INT packages). Exploitable via overly long arguments to the GENERATESCHEMA or GENERATESCHEMAS functions, allowing potential execution of arbitrary code or denial of service.

MitigationApply Oracle Critical Patch Updates (CPU) for the affected versions (9.2.0.7, 10.1.0.4). If patching is not immediately feasible, restrict execute privileges on DBMS_XMLSCHEMA and DBMS_XMLSCHEMA_INT to trusted users only, or disable the XML Database component if not required.

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
Oracle10gDatabase / datastore
Affected:= enterprise_10.1.0.4= personal_10.1.0.4= standard_10.1.0.4
Oracle9iDatabase / datastore
Affected:= standard_9.2.0.7

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle database version
    Run SELECT VERSION FROM V$INSTANCE; or SELECT BANNER FROM V$VERSION WHERE BANNER LIKE 'Oracle%'; to obtain the installed Oracle version.
    Affected if Version is 10.1.0.4 or 9.2.0.7 (exact match per affected versions listed)
  2. Confirm XML Database component is installed
    Run SELECT COMPONENT, STATUS FROM DBA_REGISTRY WHERE COMPONENT LIKE '%XML%'; or check for the existence of the XDB schema via SELECT OWNER FROM DBA_SCHEMAS WHERE SCHEMA_NAME='XDB';
    Affected if The XDB (XML Database) component is present and valid/loaded in the database
  3. Verify DBMS_XMLSCHEMA package exists
    Run SELECT OWNER, OBJECT_NAME, OBJECT_TYPE FROM DBA_OBJECTS WHERE OBJECT_NAME IN ('DBMS_XMLSCHEMA','DBMS_XMLSCHEMA_INT');
    Affected if The package DBMS_XMLSCHEMA or DBMS_XMLSCHEMA_INT exists in the database
  4. Check execute privileges on vulnerable packages
    Run SELECT GRANTEE, TABLE_NAME, PRIVILEGE FROM DBA_TAB_PRIVS WHERE TABLE_NAME IN ('DBMS_XMLSCHEMA','DBMS_XMLSCHEMA_INT') AND PRIVILEGE='EXECUTE'; to see which users/roles can execute these packages.
    Affected if Any untrusted or PUBLIC user has execute privilege on DBMS_XMLSCHEMA or DBMS_XMLSCHEMA_INT (indicating broader attack surface)
  5. Confirm GENERATESCHEMA/GENERATESCHEMAS functions are present
    Run SELECT OBJECT_NAME, OBJECT_TYPE FROM DBA_OBJECTS WHERE OBJECT_NAME IN ('GENERATESCHEMA','GENERATESCHEMAS') AND OWNER IN ('SYS','XDB');
    Affected if These functions exist in the DBMS_XMLSCHEMA package, confirming the vulnerable entry points are present

The environment is affected if running Oracle 10.1.0.4 or 9.2.0.7 with the XML Database (XDB) component installed and the DBMS_XMLSCHEMA/DBMS_XMLSCHEMA_INT packages executable by untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Updates (CPU) for the affected versions (9.2.0.7, 10.1.0.4). If patching is not immediately feasible, restrict execute privileges on DBMS_XMLSCHEMA and DBMS_XMLSCHEMA_INT to trusted users only, or disable the XML Database component if not required.

Fix this in Oracle10g Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-0272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-0272 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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