# CVE-2017-8779: Denial of service in n/a > Remote attackers can cause denial of service via memory exhaustion by sending crafted UDP packets to rpcbind or related RPC libraries. - **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 May 2017 - **Updated:** 5 Aug 2024 - **Also known as:** ALPINE-CVE-2017-8779, DEBIAN-CVE-2017-8779, DLA-936-1, DLA-937-1, DSA-3845-1, GHSA-fr7x-wc8q-h255, MGASA-2017-0183, RHBA-2017:1497, RHSA-2017:1262, RHSA-2017:1263, RHSA-2017:1267, RHSA-2017:1268, RHSA-2017:1395, SUSE-SU-2017:1306-1, SUSE-SU-2017:1314-1, SUSE-SU-2017:1328-1, SUSE-SU-2017:1336-1, SUSE-SU-2017:1468-1, UBUNTU-CVE-2017-8779, USN-4986-1, USN-4986-2, openSUSE-SU-2024:11304-1 ## What is CVE-2017-8779? CVE-2017-8779 is a high-severity denial of service vulnerability in n/a, published on 4 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) ## Which versions are affected by CVE-2017-8779? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `calamari-server` | Red Hat:ceph_storage:2::el7 | All versions | 0:1.5.6-2.el7cp | | `ceph` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `ceph-base` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `ceph-common` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `ceph-fuse` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `ceph-iscsi-cli` | Red Hat:ceph_storage:2::el7 | All versions | 0:2.0-5.el7cp | | `ceph-iscsi-config` | Red Hat:ceph_storage:2::el7 | All versions | 0:2.0-4.el7cp | | `ceph-iscsi-tools` | Red Hat:ceph_storage:2::el7 | All versions | 0:2.0-3.el7cp | | `ceph-mds` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `ceph-mon` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `ceph-osd` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `ceph-radosgw` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `ceph-selinux` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `ceph-test` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `libcephfs1` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `libcephfs1-devel` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `libntirpc` | Red Hat:ceph_storage:2::el7 | All versions | 0:1.4.3-2.el7 | | `libntirpc-debuginfo` | Red Hat:ceph_storage:2::el7 | All versions | 0:1.4.3-2.el7 | | `librados2` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `librados2-devel` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `librbd1` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `librbd1-devel` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `librgw2` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `librgw2-devel` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `libtcmu` | Red Hat:ceph_storage:2::el7 | All versions | 0:1.2.1-0.2.20170104.git3d33566.el7cp | | `nfs-ganesha` | Red Hat:ceph_storage:2::el7 | All versions | 0:2.4.5-7.el7cp | | `nfs-ganesha-debuginfo` | Red Hat:ceph_storage:2::el7 | All versions | 0:2.4.5-7.el7cp | | `nfs-ganesha-rgw` | Red Hat:ceph_storage:2::el7 | All versions | 0:2.4.5-7.el7cp | | `pcp-pmda-lio` | Red Hat:ceph_storage:2::el7 | All versions | 0:1.0-2.el7cp | | `python-cephfs` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `python-crypto` | Red Hat:ceph_storage:2::el7 | All versions | 0:2.6.1-1.2.el7cp | | `python-crypto-debuginfo` | Red Hat:ceph_storage:2::el7 | All versions | 0:2.6.1-1.2.el7cp | | `python-flask` | Red Hat:ceph_storage:2::el7 | All versions | 1:0.10.1-5.el7 | | `python-itsdangerous` | Red Hat:ceph_storage:2::el7 | All versions | 0:0.23-1.el7 | | `python-jinja2` | Red Hat:ceph_storage:2::el7 | All versions | 0:2.7.2-2.el7cp | | `python-rados` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `python-rbd` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | | `python-rtslib` | Red Hat:ceph_storage:2::el7 | All versions | 0:2.1.fb64-0.1.20170301.git3637171.el7cp | | `python-werkzeug` | Red Hat:ceph_storage:2::el7 | All versions | 0:0.9.1-1.el7 | | `rbd-mirror` | Red Hat:ceph_storage:2::el7 | All versions | 1:10.2.7-27.el7cp | Products: Libtirpc Project Libtirpc, Ntirpc Project Ntirpc, Rpcbind Project Rpcbind. ## How do I fix CVE-2017-8779? Apply the vendor's patch. ## Is CVE-2017-8779 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-8779 exists. Public exploit code: - CVE-2017-8779 aka RPCBomb (github_poc): https://github.com/drbothen/GO-RPCBOMB - RPCBind / libtirpc - Denial of Service (exploitdb) - RPC DoS targeting *nix rpcbind/libtirpc (metasploit) ## Other vulnerabilities in n/a - [CVE-2018-14621](https://insights.sbomify.com/CVE-2018-14621/): Denial of service in libtirpc (medium 5.3) - [CVE-2013-1950](https://insights.sbomify.com/CVE-2013-1950/): Denial of service in n/a (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-8779 and fix it if it is affected. What it is: CVE-2017-8779 is a high-severity denial of service vulnerability in n/a, published on 4 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-8779 exists. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-8779/ (Markdown: https://insights.sbomify.com/CVE-2017-8779/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-8779 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-8779 - OSV: https://osv.dev/vulnerability/CVE-2017-8779 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-8779/ Summaries are generated and may contain mistakes; the official description above is the record.