# CVE-2016-1251: Use after free in DBD::mysql before 4.041

> A use-after-free flaw in the Perl MySQL driver allows attackers to execute arbitrary code or cause denial of service when server-side prepared statements are enabled.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Nov 2016
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-1251, GHSA-rcfm-gwhc-4xf6, SUSE-SU-2017:0025-1, UBUNTU-CVE-2016-1251

## What is CVE-2016-1251?

CVE-2016-1251 is a high-severity use after free vulnerability in DBD::mysql before 4.041, published on 29 Nov 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a vulnerability of type use-after-free affecting DBD::mysql (aka DBD-mysql or the Database Interface (DBI) MySQL driver for Perl) 3.x and 4.x before 4.041 when used with mysql_server_prepare=1.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2016-1251?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-DBD-mysql` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 4.008-6.1 |
| `perl-DBD-mysql` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 4.008-6.1 |
| `perl-DBD-mysql` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 4.008-6.1 |

Products: Dbd-Mysql Project Dbd-Mysql.

## How do I fix CVE-2016-1251?

Upgrade to a fixed version.

## Is CVE-2016-1251 being exploited?

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

## Other vulnerabilities in DBD::mysql before 4.041

- [CVE-2017-10788](https://insights.sbomify.com/CVE-2017-10788/): Use after free in n/a (critical 9.8)
- [CVE-2014-9906](https://insights.sbomify.com/CVE-2014-9906/): Use after free in n/a (critical 9.8)
- [CVE-2015-8949](https://insights.sbomify.com/CVE-2015-8949/): Use after free in n/a (critical 9.8)
- [CVE-2016-1246](https://insights.sbomify.com/CVE-2016-1246/): Memory corruption in n/a (high 7.5)
- [CVE-2017-10789](https://insights.sbomify.com/CVE-2017-10789/): Security feature bypass in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1251 and fix it if it is affected.

What it is: CVE-2016-1251 is a high-severity use after free vulnerability in DBD::mysql before 4.041, published on 29 Nov 2016. 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-2016-1251 in the wild and no public exploit code.

Affected product: DBD::mysql before 4.041. 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-2016-1251/ (Markdown: https://insights.sbomify.com/CVE-2016-1251/index.md)
```

## Sources

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

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