dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2006-5338

HIGH · 9.0 CVSS v2.0 Published 2006-10-18
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
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 the Core RDBMS component in Oracle Database 10.1.0.5 has unknown impact and remote authenticated attack vectors related to sys.dbms_sqltune, aka Vuln# DB10. NOTE: as of 20061023, Oracle has not disputed reports from reliable third parties that DB10 is for SQL injection in DROP_SQLSET, DELETE_SQLSET, SELECT_SQLSET, and I_SET_TUNING_PARAMETER. NOTE: some of these vectors might be in DBMS_SQLTUNE_INTERNAL.

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:= 10.1.0.5= 10.2.0.0

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 www.securityfocus.com →
Recommended fix Moderate confidence

Oracle Database 10g Release 2 (10.2.0.x) with October 2006 CPU or later, or upgrade to Oracle Database 19c/21c

  1. 1. Identify the current Oracle Database 10g release version by querying SELECT * FROM v$version;
  2. 2. Determine if the system is on Oracle Database 10.1.0.5 or 10.2.0.0 specifically
  3. 3. Check Oracle Metalink/My Oracle Support for the October 2006 Critical Patch Update (CPU) that addresses this vulnerability (Oracle CPU Oct 2006)
  4. 4. Apply Oracle Critical Patch Update October 2006 (or subsequent CPU that includes the fix for CVE-2006-5338)
  5. 5. Alternatively, plan an upgrade path to a supported Oracle Database version (11g, 12c, 19c, or 21c) as Oracle 10g is end-of-life
  6. 6. After patching or upgrading, verify the fix by checking that DBMS_SQLTUNE package execution is restricted to authorized users only
  7. 7. Review SQLNET.ORA parameters and implement least-privilege access controls for the DBMS_SQLTUNE package
Caveat Oracle 10g is end-of-life; direct upgrades to 19c/21c may require intermediate steps (e.g., 11g->12c->19c). Test application compatibility thoroughly before upgrading.

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-5338 — 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-5338 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