# CVE-2014-9424: Use after free in n/a

> Remote attackers can cause denial of service or potentially execute code via a double free vulnerability in LibreSSL's DTLS handshake processing.

- **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:** No
- **Published:** 29 Dec 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8258-9w54-3r97

## What is CVE-2014-9424?

CVE-2014-9424 is a high-severity use after free vulnerability in n/a, published on 29 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Double free vulnerability in the ssl_parse_clienthello_use_srtp_ext function in d1_srtp.c in LibreSSL before 2.1.2 allows remote attackers to cause a denial of service or possibly have unspecified other impact by triggering a certain length-verification error during processing of a DTLS handshake.

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

It affects 1 product.


Products: Openbsd Libressl.

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

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

## Is CVE-2014-9424 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-35784](https://insights.sbomify.com/CVE-2023-35784/): Use after free in n/a (critical 9.8)
- [CVE-2021-46880](https://insights.sbomify.com/CVE-2021-46880/): Auth bypass in n/a (critical 9.8)
- [CVE-2015-5334](https://insights.sbomify.com/CVE-2015-5334/): Memory corruption in LibreSSL (critical 9.8)
- [CVE-2015-5333](https://insights.sbomify.com/CVE-2015-5333/): Denial of service in LibreSSL (high 7.5)
- [CVE-2018-8970](https://insights.sbomify.com/CVE-2018-8970/): Security feature bypass in n/a (high 7.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9424 is a high-severity use after free vulnerability in n/a, published on 29 Dec 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-9424 in the wild and no public exploit code.

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

## Sources

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

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