# CVE-2010-1850: Memory corruption in n/a

> Remote authenticated users can execute arbitrary code via a buffer overflow in the COM_FIELD_LIST command.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/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:** 7 Jun 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2gf7-pwpq-8w42

## What is CVE-2010-1850?

CVE-2010-1850 is a medium-severity memory corruption vulnerability in Mysql Mysql, published on 7 Jun 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in MySQL 5.0 through 5.0.91 and 5.1 before 5.1.47 allows remote authenticated users to execute arbitrary code via a COM_FIELD_LIST command with a long table name.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

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

Upgrade to a fixed version.

## Is CVE-2010-1850 being exploited?

There is no known exploitation of CVE-2010-1850 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-1850 and fix it if it is affected.

What it is: CVE-2010-1850 is a medium-severity memory corruption vulnerability in Mysql Mysql, published on 7 Jun 2010. 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-1850 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-1850/ (Markdown: https://insights.sbomify.com/CVE-2010-1850/index.md)
```

## Sources

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

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