# CVE-2002-1374: Auth bypass in n/a

> Remote attackers can gain privileges by exploiting a flaw in MySQL's password comparison logic during user change commands.

- **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:** Yes
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-rf99-cxf6-755h

## What is CVE-2002-1374?

CVE-2002-1374 is a high-severity authentication bypass vulnerability in Oracle Mysql, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The COM_CHANGE_USER command in MySQL 3.x before 3.23.54, and 4.x before 4.0.6, allows remote attackers to gain privileges via a brute force attack using a one-character password, which causes MySQL to only compare the provided password against the first character of the real password.

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

It affects 3 products.


Products: Oracle Mysql, Symantec Veritas Netbackup Advanced Reporter, Symantec Veritas Netbackup Global Data Manager.

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

Upgrade to a fixed version.

## Is CVE-2002-1374 being exploited?

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

Public exploit code:

- MySQL 3.23.x/4.0.x - 'COM_CHANGE_USER' Password Length Account (exploitdb)

## 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-2002-0969](https://insights.sbomify.com/CVE-2002-0969/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1374 is a high-severity authentication bypass vulnerability in Oracle Mysql, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1374 exists.

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-1374/ (Markdown: https://insights.sbomify.com/CVE-2002-1374/index.md)
```

## Sources

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

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