Public proof of conceptFix available

CVE-2017-8779

A public proof of concept exists; no exploitation attested.

Published2017-05-04
WeaknessCWE-770

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC

2017-05-0414:29CVE publishedNVD
2026-10-2319:23First public proof of conceptPoC-in-GitHub
2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-8779?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-8779?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Libtirpc project libtirpc

Branch	Affected	Fixed in	Source
1.0	≤ 1.0.1	no fix published	NVD

Ntirpc project ntirpc

Branch	Affected	Fixed in	Source
1.4	≤ 1.4.3	no fix published	NVD

Rpcbind project rpcbind

Branch	Affected	Fixed in	Source
0.2	≤ 0.2.4	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

read 2026-10-23 19:23 UTC

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: 1 repository, unverifieddrbothen/GO-RPCBOMB

Sources

NVDCVSS 3.07.5read 2026-10-23
NVDCVSS 2.07.8read 2026-10-23
NVDweakness (CWE)CWE-770read 2026-10-23
FIRST EPSSEPSS score81.2 %read 2026-10-23
PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published: 2017-05-04
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2017-8779?

Is CVE-2017-8779 actively exploited?

Active exploitation of CVE-2017-8779 has not been confirmed. Its EPSS score was 81.2% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-8779?

CVE-2017-8779 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database