CVE-2017-8779
high-risk
Published 2017-05-04
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.
Do I need to act?
!
81.4% chance of exploitation in next 30 days
EPSS score — higher than 19% of all CVEs
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
!
1 public exploit available
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
7
CVSS 7.5/10
High
NETWORK
/ LOW complexity
Affected Products (3)
Affected Vendors
References (38)
Mailing List
http://openwall.com/lists/oss-security/2017/05/03/12
Mailing List
http://openwall.com/lists/oss-security/2017/05/04/1
Third Party Advisory
http://www.securityfocus.com/bid/98325
Issue Tracking
https://github.com/drbothen/GO-RPCBOMB
Issue Tracking
https://github.com/guidovranken/rpcbomb/
Third Party Advisory
https://guidovranken.wordpress.com/2017/05/03/rpcbomb-remote-rpcbind-denial-of-s...
Mailing List
http://openwall.com/lists/oss-security/2017/05/03/12
and 18 more references
55
/ 100
high-risk
Severity
26/34 · High
Exploitability
20/34 · Moderate
Exposure
9/34 · Low