# CVE-2016-3178: Denial of service in n/a

> Local attackers can crash the MiniSSDPd daemon by triggering an out-of-bounds memory access via a negative length value.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-3178, GHSA-xm64-phgg-mwc9, UBUNTU-CVE-2016-3178

## What is CVE-2016-3178?

CVE-2016-3178 is a medium-severity denial of service vulnerability in n/a, published on 24 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The processRequest function in minissdpd.c in MiniSSDPd 1.2.20130907-3 allows local users to cause a denial of service (out-of-bounds memory access and daemon crash) via vectors involving a negative length value.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Miniupnp Project Minissdpd.

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

Apply the vendor's patch.

## Is CVE-2016-3178 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-3179](https://insights.sbomify.com/CVE-2016-3179/): Use after free in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-3178 is a medium-severity denial of service vulnerability in n/a, published on 24 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-3178 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-2016-3178/ (Markdown: https://insights.sbomify.com/CVE-2016-3178/index.md)
```

## Sources

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

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