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
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
DLA-936-1 | libtirpc security update |
![]() |
DLA-937-1 | rpcbind security update |
![]() |
DSA-3845-1 | libtirpc security update |
![]() |
USN-3759-1 | libtirpc vulnerabilities |
![]() |
USN-3759-2 | libtirpc vulnerabilities |
![]() |
USN-4986-1 | rpcbind vulnerability |
![]() |
USN-4986-2 | rpcbind vulnerability |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.

Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-05T16:48:22.685Z
Reserved: 2017-05-04T00:00:00
Link: CVE-2017-8779

No data.

Status : Deferred
Published: 2017-05-04T14:29:00.230
Modified: 2025-04-20T01:37:25.860
Link: CVE-2017-8779


No data.