# CVE-2003-1480: Weak cryptography in n/a

> Weak password hashing in MySQL allows attackers to decrypt stored passwords via brute force, exposing sensitive user credentials.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h8m2-gw8r-5752

## What is CVE-2003-1480?

CVE-2003-1480 is a medium-severity vulnerability in Mysql Mysql, published on 24 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MySQL 3.20 through 4.1.0 uses a weak algorithm for hashed passwords, which makes it easier for attackers to decrypt the password via brute force methods.

Weakness: CWE-310

## Which versions are affected by CVE-2003-1480?

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

## How do I fix CVE-2003-1480?

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

## Is CVE-2003-1480 being exploited?

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

Public exploit code:

- MySQL 3.x/4.0.x - Weak Password Encryption (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-2003-1480 and fix it if it is affected.

What it is: CVE-2003-1480 is a medium-severity vulnerability in Mysql Mysql, published on 24 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1480 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-2003-1480/ (Markdown: https://insights.sbomify.com/CVE-2003-1480/index.md)
```

## Sources

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

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