CVE-2017-8779: 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

Q: How do I fix CVE-2017-8779?

rpcbind: upgrade to newer than 0.2.4; libtirpc: upgrade to newer than 1.0.1; ntirpc: upgrade to newer than 1.4.3. Exact commands for each OS are on this page.

Q: Is CVE-2017-8779 being exploited?

CVE-2017-8779 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-8779 affect?

CVE-2017-8779 affects rpcbind, libtirpc, ntirpc. Severity is high (CVSS 7.5). 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 se

Q: How urgent is CVE-2017-8779?

Priority 61/100. High severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADEUPGRADEUPGRADE

CVE-2017-8779 is a high-severity flaw (CVSS 7.5) affecting rpcbind, libtirpc, ntirpc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
EPSS top 1%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	81.2% (top 1%)
CISA exploited list	No
Weakness	CWE-770
Published	2017-05-04
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: libtirpc project · ntirpc project · rpcbind project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-05-04 14:29 UTCPublished CVE record published
2026-06-17 01:26 UTCUpdated Record last modified

rpcbind project rpcbind UPGRADE

Affected: <= 0.2.4

Fixed in: newer than 0.2.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy rpcbind || rpm -q rpcbind || rpcbind --version

2. UPGRADE to newer than 0.2.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade rpcbind

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade rpcbind

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

libtirpc project libtirpc UPGRADE

Affected: <= 1.0.1

Fixed in: newer than 1.0.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libtirpc || rpm -q libtirpc || libtirpc --version

2. UPGRADE to newer than 1.0.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libtirpc

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libtirpc

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

ntirpc project ntirpc UPGRADE

Affected: <= 1.4.3

Fixed in: newer than 1.4.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy ntirpc || rpm -q ntirpc || ntirpc --version

2. UPGRADE to newer than 1.4.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ntirpc

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ntirpc

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: RPCBind / libtirpc - Denial of Service
Metasploit: RPC DoS targeting *nix rpcbind/libtirpc

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-8779?

rpcbind: upgrade to newer than 0.2.4; libtirpc: upgrade to newer than 1.0.1; ntirpc: upgrade to newer than 1.4.3. Exact commands for each OS are on this page.

Is CVE-2017-8779 being exploited?

CVE-2017-8779 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-8779 affect?

CVE-2017-8779 affects rpcbind, libtirpc, ntirpc. Severity is high (CVSS 7.5). 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 se

How urgent is CVE-2017-8779?

Priority 61/100. High severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2015-7236 HIGH 7.5 UPGRADE MITIGATE Use-after-free vulnerability in xprt_set_caller in rpcb_svc_com.c in rpcbind 0.2.1 and earlier allows remote a

References

← Back to latest CVEs