# CVE-2014-0001: Memory corruption in n/a

> A buffer overflow in the MySQL client allows remote servers to crash the client or execute arbitrary code via a long version string.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7pq3-qq22-gpw3, UBUNTU-CVE-2014-0001

## What is CVE-2014-0001?

CVE-2014-0001 is a high-severity memory corruption vulnerability in Mariadb Mariadb, published on 31 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in client/mysql.cc in Oracle MySQL and MariaDB before 5.5.35 allows remote database servers to cause a denial of service (crash) and possibly execute arbitrary code via a long server version string.

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

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

It affects 6 products.


Products: Mariadb Mariadb, Oracle Mysql, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.

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

Upgrade to a fixed version.

## Is CVE-2014-0001 being exploited?

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

## Other vulnerabilities in Mariadb Mariadb

- [CVE-2026-49261](https://insights.sbomify.com/CVE-2026-49261/): MariaDB server has unsafe parameter handling in `wsrep_notify_cmd` (critical 10.0)
- [CVE-2026-85746](https://insights.sbomify.com/CVE-2026-85746/): MariaDB: Out-of-bound buffer write on in `ST_AsText` of nested GeometryCollections (critical 9.9)
- [CVE-2026-85748](https://insights.sbomify.com/CVE-2026-85748/): MariaDB: Use-after-free with a large number of SYS_REFCURSOR's (critical 9.9)
- [CVE-2026-92262](https://insights.sbomify.com/CVE-2026-92262/): MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass. (critical 9.9)
- [CVE-2023-26785](https://insights.sbomify.com/CVE-2023-26785/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0001 is a high-severity memory corruption vulnerability in Mariadb Mariadb, published on 31 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0001 in the wild and no public exploit code.

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

## Sources

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

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