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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
n/a n/a
n/aaffected
References
- https://usn.ubuntu.com/3759-2/ ↗
- https://access.redhat.com/errata/RHSA-2017:1267 ↗
- https://usn.ubuntu.com/3759-1/ ↗
- https://access.redhat.com/errata/RHSA-2017:1262 ↗
- https://guidovranken.wordpress.com/2017/05/03/rpcbomb-remote-rpcbind-denial-of-service-patches/ ↗
- https://access.redhat.com/errata/RHSA-2017:1268 ↗
- https://github.com/drbothen/GO-RPCBOMB ↗
- https://access.redhat.com/errata/RHBA-2017:1497 ↗
- https://github.com/guidovranken/rpcbomb/ ↗
- https://security.netapp.com/advisory/ntap-20180109-0001/ ↗
- https://security.gentoo.org/glsa/201706-07 ↗
- http://www.securitytracker.com/id/1038532 ↗
- http://www.securityfocus.com/bid/98325 ↗
- http://openwall.com/lists/oss-security/2017/05/03/12 ↗
- http://openwall.com/lists/oss-security/2017/05/04/1 ↗
- https://access.redhat.com/errata/RHSA-2017:1395 ↗
- https://access.redhat.com/errata/RHSA-2017:1263 ↗
- https://www.exploit-db.com/exploits/41974/ ↗
- http://www.debian.org/security/2017/dsa-3845 ↗