CVE-2017-8779
Rpcbind Project Rpcbind vulnerability
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.
Affected products
Rpcbind, Libtirpc, Ntirpc. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Rpcbind Project Rpcbind runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- openwall.com/lists/oss-security/2017/05/03/12 · Patch
- openwall.com/lists/oss-security/2017/05/04/1 · Patch
- github.com/drbothen/GO-RPCBOMB · Patch
- github.com/guidovranken/rpcbomb/ · Patch
- www.securityfocus.com/bid/98325 · Third Party Advisory
- guidovranken.wordpress.com/2017/05/03/rpcbomb-remote-rpcbind-denial-of-service-patches/ · Third Party Advisory
- www.debian.org/security/2017/dsa-3845
- www.securitytracker.com/id/1038532
- nvd.nist.gov/vuln/detail/CVE-2017-8779
- cve.org/CVERecord?id=CVE-2017-8779
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.