# CVE-2011-2262: Denial of service in n/a

> Remote attackers can disrupt MySQL Server availability via unspecified vectors, requiring administrators to upgrade affected versions.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 18 Jan 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q74w-w5gw-g3jf

## What is CVE-2011-2262?

CVE-2011-2262 is a medium-severity denial of service vulnerability in Mysql Mysql, published on 18 Jan 2012. It can be exploited over the network.

### Official description

Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.1.x and 5.5.x allows remote attackers to affect availability via unknown vectors.

## Which versions are affected by CVE-2011-2262?

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

## How do I fix CVE-2011-2262?

Upgrade to a fixed version.

## Is CVE-2011-2262 being exploited?

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

What it is: CVE-2011-2262 is a medium-severity denial of service vulnerability in Mysql Mysql, published on 18 Jan 2012. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2011-2262 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-2011-2262/ (Markdown: https://insights.sbomify.com/CVE-2011-2262/index.md)
```

## Sources

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

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