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

> Remote attackers can crash Wireshark via crafted IrDA packets due to improper newline stripping, causing a buffer underflow.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 1 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-5161, GHSA-97j9-m52p-mwr5

## What is CVE-2014-5161?

CVE-2014-5161 is a medium-severity memory corruption vulnerability in Wireshark Wireshark, published on 1 Aug 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The dissect_log function in plugins/irda/packet-irda.c in the IrDA dissector in Wireshark 1.10.x before 1.10.9 does not properly strip '\n' characters, which allows remote attackers to cause a denial of service (buffer underflow and application crash) via a crafted packet.

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

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

It affects 1 product.


Products: Wireshark Wireshark.

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

Upgrade to a fixed version.

## Is CVE-2014-5161 being exploited?

There is no known exploitation of CVE-2014-5161 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-5161 and fix it if it is affected.

What it is: CVE-2014-5161 is a medium-severity memory corruption vulnerability in Wireshark Wireshark, published on 1 Aug 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-5161 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-5161/ (Markdown: https://insights.sbomify.com/CVE-2014-5161/index.md)
```

## Sources

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

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