CVE-2017-8798

Name: CVE-2017-8798
Creator: NVD / NIST
Published: 2017-05-11T01:29:06.21+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 24.03%

Last modified Jun 17, 2026

CVE-2017-8798 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 24.03% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability

24.03%

97.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-119

Affected Software

Vendor	Product	Versions
Miniupnp Project	Miniupnpd	1.4
Miniupnp Project	Miniupnpd	1.5
Miniupnp Project	Miniupnpd	1.7
Miniupnp Project	Miniupnpd	1.8
Miniupnp Project	Miniupnpd	1.9
Miniupnp Project	Miniupnpd	2.0

References

http://miniupnp.free.fr/files/changelog.php?file=miniupnpc-2.0.20170509.tar.gzRelease Notes, Vendor Advisory
https://github.com/tintinweb/pub/tree/master/pocs/cve-2017-8798Exploit, Third Party Advisory
https://lists.debian.org/debian-lts-announce/2020/04/msg00027.html
http://miniupnp.free.fr/files/changelog.php?file=miniupnpc-2.0.20170509.tar.gzRelease Notes, Vendor Advisory
https://github.com/tintinweb/pub/tree/master/pocs/cve-2017-8798Exploit, Third Party Advisory
https://lists.debian.org/debian-lts-announce/2020/04/msg00027.html

Timeline

Published: May 11, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-8798?

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.

How severe is CVE-2017-8798?

Severity scoring for CVE-2017-8798 is pending analysis. The EPSS model estimates a 24.03% probability of exploitation in the next 30 days.

How do I fix CVE-2017-8798?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-8798?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST