Rpcbind is a network service daemon that implements the RPC (Remote Procedure Call) port mapper, a foundational component in distributed computing environments that maps RPC service addresses to network endpoints. Its vulnerability footprint centers on resource-handling and input-validation issues—including uncontrolled resource allocation, improper input validation, and link-following weaknesses—that reflect the parsing and network-facing demands of the port-mapping protocol. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Rpcbind Project over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-8779HIGH 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 st | May 4, 2017 | 7.5 | 84 | NO | YES |
CVE-2010-2061HIGH rpcbind 0.2.0 does not properly validate (1) /tmp/portmap.xdr and (2) /tmp/rpcbind.xdr, which can be created by an attacker before the daemon is started. | Oct 29, 2019 | 7.8 | 26 | NO | NO |
CVE-2010-2064HIGH rpcbind 0.2.0 allows local users to write to arbitrary files or gain privileges via a symlink attack on (1) /tmp/portmap.xdr and (2) /tmp/rpcbind.xdr. | Oct 29, 2019 | 7.1 | 24 | NO | NO |
CVE-2015-7236HIGH Use-after-free vulnerability in xprt_set_caller in rpcb_svc_com.c in rpcbind 0.2.1 and earlier allows remote attackers to cause a denial of service (daemon crash) via crafted packe | Oct 1, 2015 | 7.5 | 21 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Rpcbind Project.
Media articles that mention a CVE ID that affects a product developed by Rpcbind Project — matched by CVE ID, not by vendor name.