dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2006-1876

HIGH · 9.0 CVSS v2.0 Published 2006-04-20
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

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 Oracle Database Server 9.2.0.7 and 10.1.0.4 has unknown impact and attack vectors in the Oracle Spatial component, aka Vuln# DB12. NOTE: details are unavailable from Oracle, but as of 20060421, they have not publicly disputed a claim by a reliable independent researcher that states that the problem is SQL injection in the (1) GEN_RID_RANGE_BY_AREA and (2) GEN_RID_RANGE functions in the MDSYS.SDO_PRIDX 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

A detailed technical summary for this CVE is being prepared.

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
Database ServerDatabase / datastore
Affected:= 9.2.0.7= 10.1.0.4

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

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 · scoped
Patch available Apply the vendor patch
Vendor patch securitytracker.com →
Recommended fix Moderate confidence

Oracle 9.2.0.8+ or Oracle 10.1.0.5+ (or Oracle 10.2.0.x/11g+)

  1. 1. Identify the Oracle Database Server version currently installed (9.2.0.7 or 10.1.0.4)
  2. 2. For Oracle 9.2.0.7: Upgrade to Oracle 9.2.0.8 or later (9.2.0.9, 9.2.0.10, or later) which contains the security fix for CVE-2006-1876 in the Spatial component
  3. 3. For Oracle 10.1.0.4: Upgrade to Oracle 10.1.0.5 or later (10.1.0.6, 10.2.0.x, or later) which contains the security fix for CVE-2006-1876 in the Spatial component
  4. 4. Apply the upgrade via Oracle's standard upgrade procedures (e.g., using DBMS_UPGRADE or manual upgrade scripts)
  5. 5. After upgrade, verify the MDSYS.SDO_PRIDX package has been updated and test that SQL injection is no longer possible via GEN_RID_RANGE_BY_AREA and GEN_RID_RANGE functions
  6. 6. Alternatively, if upgrading is not immediately feasible, apply the Oracle Critical Patch Update (CPU) for April 2006 which addresses this vulnerability
Caveat Oracle database upgrades may require testing of existing applications, backup preparation, and potential schema adjustments; review Oracle upgrade documentation for your specific version path

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-1876 — 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-1876 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