PatchTheCVErpcbind vulnerabilities and fixes
Recent CVEs affecting rpcbind, with upgrade or downgrade steps. 2 tracked.
rpcbind has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2017-05-04. Highest priority: CVE-2017-8779 (score 61/100).
- CVE-2017-8779 HIGH 7.5 UPGRADE UPGRADE 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
- 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
FAQ
How do I fix rpcbind vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is rpcbind being exploited right now?
None of the tracked rpcbind CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which rpcbind CVE should I patch first?
CVE-2017-8779 currently ranks highest (61/100): 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 .