# CVE-2010-3833: Denial of service in n/a

> Remote attackers can crash the MySQL server by sending crafted arguments to extreme-value functions, requiring a database upgrade to fix.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 14 Jan 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-75p5-8637-4fhr

## What is CVE-2010-3833?

CVE-2010-3833 is a medium-severity denial of service vulnerability in Mysql Mysql, published on 14 Jan 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MySQL 5.0 before 5.0.92, 5.1 before 5.1.51, and 5.5 before 5.5.6 does not properly propagate type errors, which allows remote attackers to cause a denial of service (server crash) via crafted arguments to extreme-value functions such as (1) LEAST and (2) GREATEST, related to KILL_BAD_DATA and a "CREATE TABLE ... SELECT."

Weakness: CWE-399

## Which versions are affected by CVE-2010-3833?

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

## How do I fix CVE-2010-3833?

Upgrade to a fixed version.

## Is CVE-2010-3833 being exploited?

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

## 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-2010-3833 and fix it if it is affected.

What it is: CVE-2010-3833 is a medium-severity denial of service vulnerability in Mysql Mysql, published on 14 Jan 2011. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-3833 in the wild and no public exploit code.

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

## Sources

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

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