CVE-2017-8779

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 82%
CISA-KEV: Not listedEPSS: 82%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
99.6%
KEV
Not listed

Published

May 4, 2017

Last Modified

May 13, 2026

References (38)

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturpcbind (0.2.3-0.6ubuntu0.18.04.2) @ bionic2026-05-22ubuntu
ubuntulibtirpc1 (0.2.5-1ubuntu0.1) @ xenial2026-05-22ubuntu
ubuntulibtirpc-dev (0.2.2-5ubuntu0.1) @ precise2026-05-22ubuntu
ubunturpcbind (0.2.3-0.2ubuntu0.16.04.1+esm1) @ xenial2026-05-22ubuntu
redhatuserspace-rcu-0:0.7.16-1.el7cp2017-06-19redhat
redhatlibntirpc-0:1.4.3-4.el7rhgs2017-06-06redhat
redhatrpcbind-0:0.2.0-13.el6_92017-05-23redhat
redhatlibtirpc-0:0.2.1-13.el6_92017-05-23redhat
redhatrpcbind-0:0.2.0-38.el7_32017-05-22redhat
redhatlibtirpc-0:0.2.4-0.8.el7_32017-05-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(10)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-04 06:28 UTCEPSS rescore
  2. 2026-07-04 06:28 UTCEPSS rescore
  3. 2026-07-01 15:03 UTCEPSS rescore
  4. 2026-06-25 13:47 UTCEPSS rescore
  5. 2026-06-24 14:02 UTCEPSS rescore
  6. 2026-06-24 14:02 UTCEPSS rescore
  7. 2026-06-23 21:30 UTCEPSS rescore
  8. 2026-06-23 21:30 UTCEPSS rescore
  9. 2026-06-23 06:00 UTCOSV refresh
  10. 2026-06-21 01:57 UTCEPSS rescore
  11. 2026-06-21 01:57 UTCEPSS rescore
  12. 2026-06-17 17:50 UTCEPSS rescore
  13. 2026-06-15 17:45 UTCEPSS rescore
  14. 2026-06-12 23:09 UTCEPSS rescore
  15. 2026-06-12 23:09 UTCEPSS rescore
  16. 2026-06-11 13:57 UTCEPSS rescore
  17. 2026-06-10 22:15 UTCEPSS rescore
  18. 2026-06-08 14:14 UTCEPSS rescore
  19. 2026-06-08 14:14 UTCEPSS rescore
  20. 2026-06-07 15:22 UTCEPSS rescore
  21. 2026-06-07 15:22 UTCEPSS rescore
  22. 2026-06-06 13:45 UTCEPSS rescore
  23. 2026-06-06 13:45 UTCEPSS rescore
  24. 2026-06-06 04:22 UTCOSV refresh
  25. 2026-06-05 22:44 UTCEPSS rescore
Show 36 more
  1. 2026-06-05 22:44 UTCEPSS rescore
  2. 2026-06-05 06:08 UTCEPSS rescore
  3. 2026-06-05 06:08 UTCEPSS rescore
  4. 2026-05-31 00:14 UTCEPSS rescore
  5. 2026-05-31 00:14 UTCEPSS rescore
  6. 2026-05-28 13:42 UTCEPSS rescore
  7. 2026-05-28 13:42 UTCEPSS rescore
  8. 2026-05-27 13:38 UTCEPSS rescore
  9. 2026-05-27 13:38 UTCEPSS rescore
  10. 2026-05-26 07:17 UTCEPSS rescore
  11. 2026-05-26 07:17 UTCEPSS rescore
  12. 2026-05-22 21:15 UTCEPSS rescore
  13. 2026-05-22 21:15 UTCEPSS rescore
  14. 2026-05-22 21:15 UTCEPSS rescore
  15. 2026-05-22 21:15 UTCEPSS rescore
  16. 2026-05-22 21:15 UTCEPSS rescore
  17. 2026-05-22 21:15 UTCEPSS rescore
  18. 2026-05-22 21:15 UTCEPSS rescore
  19. 2026-05-22 13:38 UTCEG score recompute
  20. 2026-05-22 13:38 UTCVendor advisory
  21. 2026-05-22 13:37 UTCGHSA enrichment
  22. 2026-05-21 22:40 UTCEPSS rescore
  23. 2026-05-21 22:40 UTCEPSS rescore
  24. 2026-05-20 22:37 UTCEPSS rescore
  25. 2026-05-20 22:37 UTCEPSS rescore
  26. 2026-05-20 22:37 UTCEPSS rescore
  27. 2026-05-20 22:37 UTCEPSS rescore
  28. 2026-05-20 22:37 UTCEPSS rescore
  29. 2026-05-20 22:37 UTCEPSS rescore
  30. 2026-05-20 22:37 UTCEPSS rescore
  31. 2026-05-20 22:37 UTCEPSS rescore
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-19 13:33 UTCOSV refresh
  34. 2026-05-18 21:30 UTCEPSS rescore
  35. 2026-05-18 21:30 UTCEPSS rescore
  36. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCdrbothen/GO-RPCBOMB
    First seen May 9, 2017

    CVE-2017-8779 aka RPCBomb

    Open source ↗
  • Exploit-DBEDB-41974
    First seen May 8, 2017

    RPCBind / libtirpc - Denial of Service

    Open source ↗
  • Metasploitauxiliary/dos/rpc/rpcbomb✓ verified
    First seen Jan 1, 2017

    RPC DoS targeting *nix rpcbind/libtirpc

    Open source ↗

Frequently asked(5)

What is CVE-2017-8779?
CVE-2017-8779 is a high vulnerability published on May 4, 2017. 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…
When was CVE-2017-8779 disclosed?
CVE-2017-8779 was first published in the National Vulnerability Database on May 4, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-8779 actively exploited?
CVE-2017-8779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-8779?
CVE-2017-8779 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-8779?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-8779, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-8779

Explore →

Is Your Infrastructure Affected by CVE-2017-8779?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs