# CVE-2002-0969: Memory corruption in n/a

> Local attackers can execute arbitrary code via a buffer overflow in the MySQL daemon on Windows due to insecure permissions on the configuration file.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** No
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-p742-xf6g-v4h3

## What is CVE-2002-0969?

CVE-2002-0969 is a high-severity memory corruption vulnerability in Oracle Mysql, published on 1 Sep 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in MySQL daemon (mysqld) before 3.23.50, and 4.0 beta before 4.02, on the Win32 platform, allows local users to execute arbitrary code via a long "datadir" parameter in the my.ini initialization file, whose permissions on Windows allow Full Control to the Everyone group.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2002-0969?

It affects 1 product.


Products: Oracle Mysql.

## How do I fix CVE-2002-0969?

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

## Is CVE-2002-0969 being exploited?

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

## Other vulnerabilities in Oracle Mysql

- [CVE-2016-0639](https://insights.sbomify.com/CVE-2016-0639/): Auth bypass in n/a (critical 9.8)
- [CVE-2003-0150](https://insights.sbomify.com/CVE-2003-0150/): Privilege escalation in n/a (critical 9.0)
- [CVE-2005-2572](https://insights.sbomify.com/CVE-2005-2572/): Denial of service in n/a (high 8.5)
- [CVE-2020-14878](https://insights.sbomify.com/CVE-2020-14878/): Auth bypass in MySQL Server (high 8.0)
- [CVE-2016-3440](https://insights.sbomify.com/CVE-2016-3440/): Denial of service in n/a (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0969 and fix it if it is affected.

What it is: CVE-2002-0969 is a high-severity memory corruption vulnerability in Oracle Mysql, published on 1 Sep 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-2002-0969 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-2002-0969/ (Markdown: https://insights.sbomify.com/CVE-2002-0969/index.md)
```

## Sources

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

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