# CVE-2014-6421: Use-after-free vulnerability in the SDP dissector in Wireshark 1.10.x before 1.10.10 allows remote attackers to cause a denial of service (a


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-6421, GHSA-r6wm-v578-w5jm, UBUNTU-CVE-2014-6421

## What is CVE-2014-6421?

CVE-2014-6421 is a medium-severity vulnerability in Wireshark Wireshark, published on 20 Sep 2014. 

### Official description

Use-after-free vulnerability in the SDP dissector in Wireshark 1.10.x before 1.10.10 allows remote attackers to cause a denial of service (application crash) via a crafted packet that leverages split memory ownership between the SDP and RTP dissectors.

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

It affects 1 product.


Products: Wireshark Wireshark.

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

Upgrade to a fixed version.

## Is CVE-2014-6421 being exploited?

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

## Other vulnerabilities in Wireshark Wireshark

- [CVE-2011-0444](https://insights.sbomify.com/CVE-2011-0444/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2994](https://insights.sbomify.com/CVE-2010-2994/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2995](https://insights.sbomify.com/CVE-2010-2995/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1266](https://insights.sbomify.com/CVE-2009-1266/): Other in n/a (critical 10.0)
- [CVE-2009-1210](https://insights.sbomify.com/CVE-2009-1210/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-6421 is a medium-severity vulnerability in Wireshark Wireshark, published on 20 Sep 2014. 
Exploitation: There is no known exploitation of CVE-2014-6421 in the wild and no public exploit code.

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

## Sources

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

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