# CVE-2019-12106: Use after free in n/a

> A remote attacker can crash the MiniSSDPd process via a Use After Free vulnerability in the updateDevice function.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-12106, DLA-1805-1, GHSA-cwrg-89hf-2658, UBUNTU-CVE-2019-12106

## What is CVE-2019-12106?

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

### Official description

The updateDevice function in minissdpd.c in MiniUPnP MiniSSDPd 1.4 and 1.5 allows a remote attacker to crash the process due to a Use After Free vulnerability.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2019-12106?

It affects 1 product.


Products: Miniupnp Project Miniupnpd.

## How do I fix CVE-2019-12106?

Apply the vendor's patch.

## Is CVE-2019-12106 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0230](https://insights.sbomify.com/CVE-2013-0230/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-8798](https://insights.sbomify.com/CVE-2017-8798/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-1000494](https://insights.sbomify.com/CVE-2017-1000494/): Memory corruption in n/a (high 7.8)
- [CVE-2013-0229](https://insights.sbomify.com/CVE-2013-0229/): Denial of service in n/a (high 7.8)
- [CVE-2013-1461](https://insights.sbomify.com/CVE-2013-1461/): Null dereference in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12106 and fix it if it is affected.

What it is: CVE-2019-12106 is a high-severity use after free vulnerability in n/a, published on 15 May 2019. 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-2019-12106 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-2019-12106/ (Markdown: https://insights.sbomify.com/CVE-2019-12106/index.md)
```

## Sources

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

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