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

> Remote authenticated users can cause a denial of service in MySQL by modifying InnoDB configuration parameters and executing DDL statements.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2f85-2599-xgq8

## What is CVE-2010-3676?

CVE-2010-3676 is a medium-severity denial of service vulnerability in Mysql Mysql, published on 11 Jan 2011. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

storage/innobase/dict/dict0crea.c in mysqld in Oracle MySQL 5.1 before 5.1.49 allows remote authenticated users to cause a denial of service (assertion failure) by modifying the (1) innodb_file_format or (2) innodb_file_per_table configuration parameters for the InnoDB storage engine, then executing a DDL statement.

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

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

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

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

## Is CVE-2010-3676 being exploited?

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

Public exploit code:

- Oracle MySQL < 5.1.49 - 'DDL' Statements Denial of Service (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-2010-3676 and fix it if it is affected.

What it is: CVE-2010-3676 is a medium-severity denial of service vulnerability in Mysql Mysql, published on 11 Jan 2011. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-3676 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-2010-3676/ (Markdown: https://insights.sbomify.com/CVE-2010-3676/index.md)
```

## Sources

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

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