CVE-2017-8779

HIGHNVD 7.58.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 81% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
8.9EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 81%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 81%CVSS: 7.5Exploit: Metasploit · epss top5pct · epss high · public exploitExposed services: Not assessed

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
8.9HIGHhigh confidence
EG Risk
77
EG Risk 77/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity89% × 45%
Exploitation81% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
81%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

May 4, 2017

Last Modified

June 17, 2026

References (38)

Patch Availability(10)

Vendor / EcosystemFix (by version range) / 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.

Affected Packages

(34 across 24 ecosystems)
Debian:11(3)
PackageVulnerable rangeFix by version rangeDependents
libtirpc—
  • every version up to 0.2.5-1.2: fixed in 0.2.5-1.2
—
ntirpc—
  • every version up to 1.4.4-1: fixed in 1.4.4-1
—
rpcbind—
  • every version up to 0.2.3-0.6: fixed in 0.2.3-0.6
—
Debian:12(3)
PackageVulnerable rangeFix by version rangeDependents
libtirpc—
  • every version up to 0.2.5-1.2: fixed in 0.2.5-1.2
—
ntirpc—
  • every version up to 1.4.4-1: fixed in 1.4.4-1
—
rpcbind—
  • every version up to 0.2.3-0.6: fixed in 0.2.3-0.6
—
Debian:13(3)
PackageVulnerable rangeFix by version rangeDependents
libtirpc—
  • every version up to 0.2.5-1.2: fixed in 0.2.5-1.2
—
ntirpc—
  • every version up to 1.4.4-1: fixed in 1.4.4-1
—
rpcbind—
  • every version up to 0.2.3-0.6: fixed in 0.2.3-0.6
—
Debian:14(3)
PackageVulnerable rangeFix by version rangeDependents
libtirpc—
  • every version up to 0.2.5-1.2: fixed in 0.2.5-1.2
—
ntirpc—
  • every version up to 1.4.4-1: fixed in 1.4.4-1
—
rpcbind—
  • every version up to 0.2.3-0.6: fixed in 0.2.3-0.6
—
Debian:7(2)
PackageVulnerable rangeFix by version rangeDependents
libtirpc0.2.2-5
  • every version up to 0.2.2-5+deb7u1: fixed in 0.2.2-5+deb7u1
—
rpcbind0.2.0-8, 0.2.0-8+deb7u1
  • every version up to 0.2.0-8+deb7u2: fixed in 0.2.0-8+deb7u2
—
Debian:8(2)
PackageVulnerable rangeFix by version rangeDependents
libtirpc0.2.5-1
  • every version up to 0.2.5-1+deb8u1: fixed in 0.2.5-1+deb8u1
—
rpcbind0.2.1-6, 0.2.1-6+deb8u1
  • every version up to 0.2.1-6+deb8u2: fixed in 0.2.1-6+deb8u2
—
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
rpcbind—
  • every version up to 0.2.4-r0: fixed in 0.2.4-r0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

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 2× in last 7d / 10× 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.

Showing the most recent 100 of 103 total refreshes for this CVE.

  1. 2026-09-30 14:59 UTCEPSS rescore
  2. 2026-09-30 09:44 UTCEG score recompute
  3. 2026-09-26 15:53 UTCEPSS rescore
  4. 2026-09-24 13:59 UTCEPSS rescore
  5. 2026-09-21 20:27 UTCEPSS rescore
  6. 2026-09-18 12:06 UTCOSV refresh
  7. 2026-09-17 19:22 UTCEPSS rescore
  8. 2026-09-17 19:22 UTCEPSS rescore
  9. 2026-09-13 16:42 UTCEPSS rescore
  10. 2026-09-11 09:31 UTCEPSS rescore
  11. 2026-09-05 15:24 UTCEPSS rescore
  12. 2026-09-04 13:56 UTCEPSS rescore
  13. 2026-08-30 19:13 UTCEPSS rescore
  14. 2026-08-30 12:42 UTCOSV refresh
  15. 2026-08-28 21:36 UTCEPSS rescore
  16. 2026-08-26 14:41 UTCEPSS rescore
  17. 2026-08-19 16:59 UTCEPSS rescore
  18. 2026-08-18 13:43 UTCEPSS rescore
  19. 2026-08-16 02:10 UTCEPSS rescore
  20. 2026-08-15 01:26 UTCEPSS rescore
  21. 2026-08-14 02:19 UTCOSV refresh
  22. 2026-08-12 13:46 UTCEPSS rescore
  23. 2026-07-30 16:24 UTCEPSS rescore
  24. 2026-07-30 01:26 UTCEPSS rescore
  25. 2026-07-29 07:04 UTCOSV refresh
Show 75 more
  1. 2026-07-28 15:32 UTCEPSS rescore
  2. 2026-07-26 14:51 UTCEPSS rescore
  3. 2026-07-26 14:51 UTCEPSS rescore
  4. 2026-07-23 14:15 UTCEPSS rescore
  5. 2026-07-23 01:31 UTCEG score recompute▲ 1.40
  6. 2026-07-22 22:10 UTCEG score recompute
  7. 2026-07-22 14:04 UTCEPSS rescore
  8. 2026-07-21 15:21 UTCEPSS rescore
  9. 2026-07-20 17:04 UTCEPSS rescore
  10. 2026-07-20 17:04 UTCEPSS rescore
  11. 2026-07-19 14:28 UTCEPSS rescore
  12. 2026-07-19 14:28 UTCEPSS rescore
  13. 2026-07-15 16:55 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-12 05:43 UTCEPSS rescore
  16. 2026-07-11 23:41 UTCOSV refresh
  17. 2026-07-09 19:06 UTCEPSS rescore
  18. 2026-07-04 06:28 UTCEPSS rescore
  19. 2026-07-04 06:28 UTCEPSS rescore
  20. 2026-07-01 15:03 UTCEPSS rescore
  21. 2026-06-25 13:47 UTCEPSS rescore
  22. 2026-06-24 14:02 UTCEPSS rescore
  23. 2026-06-24 14:02 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-23 21:30 UTCEPSS rescore
  26. 2026-06-23 06:00 UTCOSV refresh
  27. 2026-06-21 01:57 UTCEPSS rescore
  28. 2026-06-21 01:57 UTCEPSS rescore
  29. 2026-06-17 17:50 UTCEPSS rescore
  30. 2026-06-15 17:45 UTCEPSS rescore
  31. 2026-06-12 23:09 UTCEPSS rescore
  32. 2026-06-12 23:09 UTCEPSS rescore
  33. 2026-06-11 13:57 UTCEPSS rescore
  34. 2026-06-10 22:15 UTCEPSS rescore
  35. 2026-06-08 14:14 UTCEPSS rescore
  36. 2026-06-08 14:14 UTCEPSS rescore
  37. 2026-06-07 15:22 UTCEPSS rescore
  38. 2026-06-07 15:22 UTCEPSS rescore
  39. 2026-06-06 13:45 UTCEPSS rescore
  40. 2026-06-06 13:45 UTCEPSS rescore
  41. 2026-06-06 04:22 UTCOSV refresh
  42. 2026-06-05 22:44 UTCEPSS rescore
  43. 2026-06-05 22:44 UTCEPSS rescore
  44. 2026-06-05 06:08 UTCEPSS rescore
  45. 2026-06-05 06:08 UTCEPSS rescore
  46. 2026-05-31 00:14 UTCEPSS rescore
  47. 2026-05-31 00:14 UTCEPSS rescore
  48. 2026-05-28 13:42 UTCEPSS rescore
  49. 2026-05-28 13:42 UTCEPSS rescore
  50. 2026-05-27 13:38 UTCEPSS rescore
  51. 2026-05-27 13:38 UTCEPSS rescore
  52. 2026-05-26 07:17 UTCEPSS rescore
  53. 2026-05-26 07:17 UTCEPSS rescore
  54. 2026-05-22 21:15 UTCEPSS rescore
  55. 2026-05-22 21:15 UTCEPSS rescore
  56. 2026-05-22 21:15 UTCEPSS rescore
  57. 2026-05-22 21:15 UTCEPSS rescore
  58. 2026-05-22 21:15 UTCEPSS rescore
  59. 2026-05-22 21:15 UTCEPSS rescore
  60. 2026-05-22 21:15 UTCEPSS rescore
  61. 2026-05-22 13:38 UTCEG score recompute
  62. 2026-05-22 13:38 UTCVendor advisory
  63. 2026-05-22 13:37 UTCGHSA enrichment
  64. 2026-05-21 22:40 UTCEPSS rescore
  65. 2026-05-21 22:40 UTCEPSS rescore
  66. 2026-05-20 22:37 UTCEPSS rescore
  67. 2026-05-20 22:37 UTCEPSS rescore
  68. 2026-05-20 22:37 UTCEPSS rescore
  69. 2026-05-20 22:37 UTCEPSS rescore
  70. 2026-05-20 22:37 UTCEPSS rescore
  71. 2026-05-20 22:37 UTCEPSS rescore
  72. 2026-05-20 22:37 UTCEPSS rescore
  73. 2026-05-20 22:37 UTCEPSS rescore
  74. 2026-05-20 22:37 UTCEPSS rescore
  75. 2026-05-19 13:33 UTCOSV refresh

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.

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

    RPC DoS targeting *nix rpcbind/libtirpc

    Open source ↗
  • 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 ↗

Related CVEs(same product + same vendor + same CWE)

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 on May 4, 2017, with the most recent update on June 17, 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. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 81% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-8779?
CVE-2017-8779 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9 (HIGH).
How do I remediate CVE-2017-8779?
A fix for CVE-2017-8779 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs