# CVE-2006-0903: Security feature bypass in n/a

> Local users can bypass MySQL logging mechanisms by injecting NULL characters into SQL queries, hiding their activities from audit trails.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4qqq-9pg4-j3vh

## What is CVE-2006-0903?

CVE-2006-0903 is a medium-severity vulnerability in Mysql Mysql, published on 27 Feb 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MySQL 5.0.18 and earlier allows local users to bypass logging mechanisms via SQL queries that contain the NULL character, which are not properly handled by the mysql_real_query function.  NOTE: this issue was originally reported for the mysql_query function, but the vendor states that since mysql_query expects a null character, this is not an issue for mysql_query.

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

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

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

Upgrade to a fixed version.

## Is CVE-2006-0903 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0903 exists.

Public exploit code:

- MySQL 5.0.18 - Query Logging Bypass (exploitdb)

## Other vulnerabilities in Mysql Mysql

- [CVE-2004-0627](https://insights.sbomify.com/CVE-2004-0627/): Auth bypass in n/a (critical 10.0)
- [CVE-2004-0628](https://insights.sbomify.com/CVE-2004-0628/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-2446](https://insights.sbomify.com/CVE-2009-2446/): Other in n/a (high 8.5)
- [CVE-2012-0553](https://insights.sbomify.com/CVE-2012-0553/): Memory corruption in n/a (high 7.5)
- [CVE-2013-1492](https://insights.sbomify.com/CVE-2013-1492/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0903 is a medium-severity vulnerability in Mysql Mysql, published on 27 Feb 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0903 exists.

Affected product: Mysql Mysql. 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-0903/ (Markdown: https://insights.sbomify.com/CVE-2006-0903/index.md)
```

## Sources

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

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