# CVE-2006-0547: Privilege escalation in n/a

> Authenticated users can execute arbitrary SQL as SYS and bypass audit logs via TNS protocol manipulation, requiring immediate patching.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-559x-r5hp-v76r

## What is CVE-2006-0547?

CVE-2006-0547 is a high-severity vulnerability in Oracle Database Server, published on 4 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Oracle 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.

## Which versions are affected by CVE-2006-0547?

It affects 1 product.


Products: Oracle Database Server.

## How do I fix CVE-2006-0547?

No fix has been published for CVE-2006-0547 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-0547 being exploited?

There is no known exploitation of CVE-2006-0547 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Database Server

- [CVE-2015-4863](https://insights.sbomify.com/CVE-2015-4863/): Other in n/a (critical 10.0)
- [CVE-2013-1534](https://insights.sbomify.com/CVE-2013-1534/): Other in n/a (critical 10.0)
- [CVE-2010-0071](https://insights.sbomify.com/CVE-2010-0071/): Other in n/a (critical 10.0)
- [CVE-2009-1979](https://insights.sbomify.com/CVE-2009-1979/): Other in n/a (critical 10.0)
- [CVE-2009-1985](https://insights.sbomify.com/CVE-2009-1985/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0547 and fix it if it is affected.

What it is: CVE-2006-0547 is a high-severity vulnerability in Oracle Database Server, published on 4 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0547 in the wild and no public exploit code.

Affected product: Oracle Database Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-0547/ (Markdown: https://insights.sbomify.com/CVE-2006-0547/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-0547
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-0547
- OSV: https://osv.dev/vulnerability/CVE-2006-0547

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-0547/
Summaries are generated and may contain mistakes; the official description above is the record.