CVE-2006-0547
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 · uneditedOracle Database 8i, 9i, and 10g allow remote authenticated users to execute arbitrary SQL statements in the context of the SYS user and bypass audit logging, including statements to create new privileged database accounts, via a modified AUTH_ALTER_SESSION attribute in the authentication phase of the Transparent Network Substrate (TNS) protocol. NOTE: due to the lack of relevant details from the Oracle advisory, a separate CVE is being created since it cannot be conclusively proven that this issue has been addressed by Oracle. It is possible that this is the same issue as Oracle Vuln# DB18 from the January 2006 CPU, in which case this would be subsumed by CVE-2006-0265.
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 confidenceOracle Database 8i, 9g, and 10g vulnerability allowing remote authenticated users to execute arbitrary SQL statements in SYS context by modifying the AUTH_ALTER_SESSION attribute during TNS protocol authentication. The flaw also enables bypassing audit logging, permitting creation of privileged database accounts.
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= 9.2.0.6= 9.2.0.7= 10.1.0.3= 10.1.0.4= 10.1.0.5= 10.2.0.1CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/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 using SQL*Plus or SQL Developer and run: SELECT VERSION FROM V$INSTANCE;Affected if The version matches any of: 8.1.7.4, 9.2.0.6, 9.2.0.7, 10.1.0.3, 10.1.0.4, 10.1.0.5, or 10.2.0.1
-
Verify TNS listener network exposureExamine the listener.ora file (typically in $ORACLE_HOME/network/admin/) and check if the LISTENER is configured with a non-restricted ADDRESS or uses TCP protocol on an exposed IP. Use command: lsnrctl status LISTENERAffected if The TNS listener accepts connections from untrusted networks or IP addresses outside the trusted environment
-
Confirm audit logging is enabledRun the query: SELECT VALUE FROM V$PARAMETER WHERE NAME = 'audit_trail';Affected if Audit trail is set to NONE, DB, or OS, but the vulnerability allows bypassing this logging mechanism entirely when exploited
-
Check for privileged account creation eventsReview audit records or alert log for unexpected creation of accounts with DBA, SYSDBA, or privileged roles that were not initiated by authorized administratorsAffected if Privileged accounts appear in the database without legitimate creation records in the audit trail
You are affected if you run any of the specific versions (8.1.7.4, 9.2.0.6, 9.2.0.7, 10.1.0.3-10.1.0.5, or 10.2.0.1) and your TNS listener is accessible to remote authenticated users on untrusted networks.
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 the Oracle Critical Patch Update (CPU) addressing DB18 from January 2006 (CVE-2006-0265 may subsume this), and restrict network access to the TNS listener to reduce attack surface.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-0547 — 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-0547 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