# CVE-2014-0430: Denial of service in n/a

> Remote authenticated users can cause a denial of service in MySQL Server via unspecified vectors in the Performance Schema component.

- **Severity:** Low 2.8 (`AV:N/AC:M/Au:M/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:** No
- **Published:** 15 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-29pr-8c85-84q5

## What is CVE-2014-0430?

CVE-2014-0430 is a low-severity denial of service vulnerability in Oracle Mysql, published on 15 Jan 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.6.13 and earlier allows remote authenticated users to affect availability via unknown vectors related to Performance Schema.

## Which versions are affected by CVE-2014-0430?

It affects 1 product.


Products: Oracle Mysql.

## How do I fix CVE-2014-0430?

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

## Is CVE-2014-0430 being exploited?

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

## Other vulnerabilities in Oracle Mysql

- [CVE-2016-0639](https://insights.sbomify.com/CVE-2016-0639/): Auth bypass in n/a (critical 9.8)
- [CVE-2003-0150](https://insights.sbomify.com/CVE-2003-0150/): Privilege escalation in n/a (critical 9.0)
- [CVE-2005-2572](https://insights.sbomify.com/CVE-2005-2572/): Denial of service in n/a (high 8.5)
- [CVE-2020-14878](https://insights.sbomify.com/CVE-2020-14878/): Auth bypass in MySQL Server (high 8.0)
- [CVE-2002-0969](https://insights.sbomify.com/CVE-2002-0969/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0430 and fix it if it is affected.

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

Affected product: Oracle 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-2014-0430/ (Markdown: https://insights.sbomify.com/CVE-2014-0430/index.md)
```

## Sources

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

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