CVE-2006-0271
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 & Downgrade component of Oracle Database server 8.1.7.4, 9.0.1.5, 9.2.0.7, and 10.1.0.4 has unspecified impact and attack vectors, as identified by Oracle Vuln# DB28. NOTE: details are unavailable from Oracle, but they have not publicly disputed a claim by a reliable independent researcher that states that the problem is SQL injection in the DBMS_REGISTRY package in certain parameters to the (1) IS_COMPONENT, (2) GET_COMP_OPTION, (3) DISABLE_DDL_TRIGGERS, (4) SCRIPT_EXISTS, (5) COMP_PATH, (6) GATHER_STATS, (7) NOTHING_SCRIPT, and (8) VALIDATE_COMPONENTS functions.
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 the DBMS_REGISTRY package of Oracle Database versions 8.1.7.4, 9.0.1.5, 9.2.0.7, and 10.1.0.4. The vulnerability affects eight functions (IS_COMPONENT, GET_COMP_OPTION, DISABLE_DDL_TRIGGERS, SCRIPT_EXISTS, COMP_PATH, GATHER_STATS, NOTHING_SCRIPT, and VALIDATE_COMPONENTS), allowing unauthenticated attackers to execute arbitrary SQL commands via unsanitized parameters.
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= 8.1.7.4= enterprise_10.1.0.4= personal_10.1.0.4= standard_10.1.0.4= enterprise_8.1.7.4= standard_8.1.7.4= enterprise_9.0.1.5= standard_9.2.0.7CVSS 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
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/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.
-
Identify Oracle Database versionConnect to the database as a privileged user and run: SELECT * FROM V$VERSION; or SELECT VERSION FROM PRODUCT_COMPONENT_VERSION WHERE PRODUCT LIKE 'Oracle Database%';Affected if The displayed version matches 8.1.7.4, 9.0.1.5, 9.2.0.7, or 10.1.0.4 exactly, or falls within the 8.1.7.x, 9.0.1.x, 9.2.0.x, or 10.1.0.x families that include these specific patch levels.
-
Verify DBMS_REGISTRY package existsQuery DBA_OBJECTS: SELECT OBJECT_NAME, OBJECT_TYPE, STATUS FROM DBA_OBJECTS WHERE OBJECT_NAME = 'DBMS_REGISTRY' AND OBJECT_TYPE = 'PACKAGE';Affected if The package is present in the database (any result returned indicates the potentially vulnerable component is installed).
-
Check execute权限 on DBMS_REGISTRYQuery DBA_TAB_PRIVS: SELECT GRANTEE, TABLE_NAME, PRIVILEGE FROM DBA_TAB_PRIVS WHERE TABLE_NAME = 'DBMS_REGISTRY';Affected if PUBLIC or unauthorized schemas have EXECUTE privilege on the DBMS_REGISTRY package, indicating the attack surface is accessible to unauthenticated users.
-
Confirm vulnerable functions existQuery USER_PROCEDURES or DBA_PROCEDURES: SELECT PROCEDURE_NAME FROM USER_PROCEDURES WHERE OBJECT_NAME = 'DBMS_REGISTRY'; for each of these: IS_COMPONENT, GET_COMP_OPTION, DISABLE_DDL_TRIGGERS, SCRIPT_EXISTS, COMP_PATH, GATHER_STATS, NOTHING_SCRIPT, VALIDATE_COMPONENTSAffected if One or more of these eight functions are present in the DBMS_REGISTRY package, confirming the vulnerable entry points exist.
-
Check for recent unauthorized DDL or SQL activityReview DBA_AUDIT_TRAIL or unified audit trails for unusual executions of DBMS_REGISTRY procedures, especially those with string parameters that may indicate injection attempts.Affected if Audit records show unexpected executions of DBMS_REGISTRY functions, particularly with anomalous parameter patterns.
You are affected if your Oracle Database version is 8.1.7.4, 9.0.1.5, 9.2.0.7, or 10.1.0.4 AND the DBMS_REGISTRY package with its eight vulnerable functions is installed and accessible to PUBLIC or unauthorized users.
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 Oracle Critical Patch Updates for the relevant version or upgrade to a supported Oracle Database version. Additionally, restrict access to the DBMS_REGISTRY package and implement least-privilege database user accounts.
Oracle 19c or later (currently supported Long Term Release)
- Migrate from the affected Oracle 8i/9i/10g versions to a currently supported Oracle Database release (Oracle 19c, 21c, or 23c)
- Oracle 8i, 9i, and 10g have reached extended support end-of-life and no longer receive Critical Patch Updates
- Contact Oracle Support to discuss upgrade options and obtain upgrade documentation for your specific deployment
- If immediate upgrade is not feasible, restrict network access to the database server to minimize attack surface
- Ensure the DBMS_REGISTRY package is not exposed to untrusted network segments or unauthorized users
- Review and apply any available legacy patches from Oracle if under extended support contract
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-2006-0271 — 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-2006-0271 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