CVE-2017-8779
Last modified
CVE-2017-8779 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 81.92% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Rpcbind Project | Rpcbind | <= 0.2.4 |
| Libtirpc Project | Libtirpc | <= 1.0.1 |
| Ntirpc Project | Ntirpc | <= 1.4.3 |
References
- http://openwall.com/lists/oss-security/2017/05/03/12Mailing List, Patch, Third Party Advisory
- http://openwall.com/lists/oss-security/2017/05/04/1Mailing List, Patch, Third Party Advisory
- http://www.securityfocus.com/bid/98325Third Party Advisory, VDB Entry
- https://github.com/drbothen/GO-RPCBOMBIssue Tracking, Patch, Third Party Advisory
- https://github.com/guidovranken/rpcbomb/Issue Tracking, Patch, Third Party Advisory
- http://openwall.com/lists/oss-security/2017/05/03/12Mailing List, Patch, Third Party Advisory
- http://openwall.com/lists/oss-security/2017/05/04/1Mailing List, Patch, Third Party Advisory
- http://www.securityfocus.com/bid/98325Third Party Advisory, VDB Entry
- https://github.com/drbothen/GO-RPCBOMBIssue Tracking, Patch, Third Party Advisory
- https://github.com/guidovranken/rpcbomb/Issue Tracking, Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-8779?
How severe is CVE-2017-8779?
How do I fix CVE-2017-8779?
Are you affected by CVE-2017-8779?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
