# CVE-2014-9381: Integer overflow in n/a

> Remote attackers can crash Ettercap via a crafted password due to an integer signedness error causing excessive memory allocation.

- **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:** 19 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-9381, GHSA-48qw-96c7-m2c9

## What is CVE-2014-9381?

CVE-2014-9381 is a medium-severity vulnerability in n/a, published on 19 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer signedness error in the dissector_cvs function in dissectors/ec_cvs.c in Ettercap 0.8.1 allows remote attackers to cause a denial of service (crash) via a crafted password, which triggers a large memory allocation.

Weakness: CWE-189

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

It affects 1 product.


Products: Ettercap-Project Ettercap.

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

Upgrade to a fixed version.

## Is CVE-2014-9381 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-3843](https://insights.sbomify.com/CVE-2010-3843/): Memory corruption in ettercap (high 7.8)
- [CVE-2014-6395](https://insights.sbomify.com/CVE-2014-6395/): Memory corruption in n/a (high 7.5)
- [CVE-2014-6396](https://insights.sbomify.com/CVE-2014-6396/): Memory corruption in n/a (high 7.5)
- [CVE-2014-9376](https://insights.sbomify.com/CVE-2014-9376/): Integer overflow in n/a (high 7.5)
- [CVE-2014-9377](https://insights.sbomify.com/CVE-2014-9377/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9381 is a medium-severity vulnerability in n/a, published on 19 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-9381 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-9381/ (Markdown: https://insights.sbomify.com/CVE-2014-9381/index.md)
```

## Sources

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

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