Patchfirst
CVE-2017-8779 Public exploit EPSS 81.2%

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…

No fixed version listed yet.Check the vendor advisory. References ↓

Summary

The flaw lies in 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), which do not account for the maximum RPC data size when allocating memory for XDR strings. An attacker with network access can send a crafted UDP packet to port 111 to exhaust memory on the affected service, causing denial of service, with no authentication or user interaction required.

Official description · CVE.org

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.

Breakdown
24.9 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15

Public exploit code (Exploit-DB) appeared 4 days after disclosure. No confirmed exploitation is recorded.

  1. Disclosedday 0
  2. Public exploit codeExploit-DB+4 days

2 related vulnerabilities in the same code over 3 days.

Linked vulnerabilitiesLinked by evidence that a fix failed or the same code was patched again. Oldest first.

  1. This CVECVE-2017-8779rpcbind through 0.2.4, LIBTIRPC through 1.0.1 and 1.0.2-rc…4 May 2017
  2. relatedLow

    Why these are linked:

    • Stated in the CVE text…er deserialization, which allows remote attackers to cause a denial of service (virtual memory allocation, or memory consumption if an overcommit setting is not used) via a crafted UDP packet to port 111, a related issue to CVE-2017-8779.
    CVE-2017-8804The xdr_bytes and xdr_string functions in the GNU C Library (aka…7 May 2017
↑ ↓ chooseEnter openEsc close