# CVE-2004-0957: Privilege escalation in n/a

> Local users with specific database privileges can escalate access to similarly named databases, enabling unauthorized activities.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 21 Oct 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hx63-8p37-c3fh

## What is CVE-2004-0957?

CVE-2004-0957 is a medium-severity vulnerability in Oracle Mysql, published on 21 Oct 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unknown vulnerability in MySQL 3.23.58 and earlier, when a local user has privileges for a database whose name includes a "_" (underscore), grants privileges to other databases that have similar names, which can allow the user to conduct unauthorized activities.

## Which versions are affected by CVE-2004-0957?

It affects 7 products.


Products: Openpkg Openpkg, Oracle Mysql, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Suse Suse Linux, Trustix Secure Linux, Ubuntu Ubuntu Linux.

## How do I fix CVE-2004-0957?

Upgrade to a fixed version.

## Is CVE-2004-0957 being exploited?

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

## Other vulnerabilities in Oracle Mysql

- [CVE-2004-1019](https://insights.sbomify.com/CVE-2004-1019/): Deserialization in n/a (critical 10.0)
- [CVE-2004-1065](https://insights.sbomify.com/CVE-2004-1065/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0413](https://insights.sbomify.com/CVE-2004-0413/): Integer overflow in n/a (critical 10.0)
- [CVE-2002-0985](https://insights.sbomify.com/CVE-2002-0985/): Command injection in n/a (high 7.5)
- [CVE-2003-0147](https://insights.sbomify.com/CVE-2003-0147/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0957 and fix it if it is affected.

What it is: CVE-2004-0957 is a medium-severity vulnerability in Oracle Mysql, published on 21 Oct 2004. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0957 in the wild and no public exploit code.

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

## Sources

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

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