CVE-2017-8779

Public Exploit

Description

rpcbind through 0.2.4, LIBTIRPC through 1.0.1 and 1.0.2-rc through 1.0.2-rc3, and NTIRPC through 1.4.3 do not consider the maximum RPC data size during memory allocation for XDR strings, which allows remote attackers to cause a denial of service (memory consumption with no subsequent free) via a crafted UDP packet to port 111, aka rpcbomb.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 84.20% Top 5%
Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory gentoo.org Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory debian.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://usn.ubuntu.com/3759-2/ vendor advisory
https://access.redhat.com/errata/RHSA-2017:1267 vendor advisory
https://usn.ubuntu.com/3759-1/ vendor advisory
https://access.redhat.com/errata/RHSA-2017:1262 vendor advisory
https://guidovranken.wordpress.com/2017/05/03/rpcbomb-remote-rpcbind-denial-of-service-patches/ third party advisory
https://access.redhat.com/errata/RHSA-2017:1268 vendor advisory
https://github.com/drbothen/GO-RPCBOMB issue tracking third party advisory patch
https://access.redhat.com/errata/RHBA-2017:1497 vendor advisory
https://github.com/guidovranken/rpcbomb/ issue tracking third party advisory patch
https://security.netapp.com/advisory/ntap-20180109-0001/
https://security.gentoo.org/glsa/201706-07 vendor advisory
http://www.securitytracker.com/id/1038532 vdb entry
http://www.securityfocus.com/bid/98325 vdb entry third party advisory
http://openwall.com/lists/oss-security/2017/05/03/12 mailing list third party advisory patch
http://openwall.com/lists/oss-security/2017/05/04/1 mailing list third party advisory patch
https://access.redhat.com/errata/RHSA-2017:1395 vendor advisory
https://access.redhat.com/errata/RHSA-2017:1263 vendor advisory
https://www.exploit-db.com/exploits/41974/ exploit
http://www.debian.org/security/2017/dsa-3845 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-8779?
CVE-2017-8779 has been scored as a high severity vulnerability.
How to fix CVE-2017-8779?
To fix CVE-2017-8779, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-8779 being actively exploited in the wild?
It is possible that CVE-2017-8779 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~84% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.