# CVE-2017-8798: Integer overflow in n/a

> Remote attackers can cause denial of service in MiniUPnP library due to an integer signedness error.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 11 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-8798, DLA-2197-1, DLA-949-1, GHSA-3wfp-98cg-vgm9, MGASA-2017-0313, UBUNTU-CVE-2017-8798, USN-3298-1, openSUSE-SU-2024:11055-1

## What is CVE-2017-8798?

CVE-2017-8798 is a critical vulnerability in n/a, published on 11 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer signedness error in MiniUPnP MiniUPnPc v1.4.20101221 through v2.0 allows remote attackers to cause a denial of service or possibly have unspecified other impact.

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

## Which versions are affected by CVE-2017-8798?

It affects 1 product.


Products: Miniupnp Project Miniupnpd.

## How do I fix CVE-2017-8798?

Apply the vendor's patch.

## Is CVE-2017-8798 being exploited?

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

Public exploit code:

- MiniUPnP MiniUPnPc < 2.0 - Remote Denial of Service (exploitdb)

## 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-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)
- [CVE-2013-1462](https://insights.sbomify.com/CVE-2013-1462/): Integer overflow in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8798 and fix it if it is affected.

What it is: CVE-2017-8798 is a critical vulnerability in n/a, published on 11 May 2017. 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-2017-8798 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-2017-8798/ (Markdown: https://insights.sbomify.com/CVE-2017-8798/index.md)
```

## Sources

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

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