# CVE-2018-1111: Command injection in dhcp > A malicious DHCP server can execute arbitrary commands with root privileges on Linux systems using NetworkManager due to a command injection flaw in the DHCP client script. - **Severity:** High 7.5 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 May 2018 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-5jw9-5ff9-vr5p, RHSA-2018:1453, RHSA-2018:1454, RHSA-2018:1455, RHSA-2018:1456, RHSA-2018:1457, RHSA-2018:1458, RHSA-2018:1459, RHSA-2018:1460, RHSA-2018:1461 ## What is CVE-2018-1111? CVE-2018-1111 is a high-severity command injection vulnerability in Fedoraproject Fedora, published on 17 May 2018. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description DHCP packages in Red Hat Enterprise Linux 6 and 7, Fedora 28, and earlier are vulnerable to a command injection flaw in the NetworkManager integration script included in the DHCP client. A malicious DHCP server, or an attacker on the local network able to spoof DHCP responses, could use this flaw to execute arbitrary commands with root privileges on systems using NetworkManager and configured to obtain network configuration using the DHCP protocol. Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command) ## Which versions are affected by CVE-2018-1111? It affects 7 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `dhclient` | Red Hat:enterprise_linux:6::client | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp` | Red Hat:enterprise_linux:6::client | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-common` | Red Hat:enterprise_linux:6::client | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-devel` | Red Hat:enterprise_linux:6::client | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhclient` | Red Hat:enterprise_linux:6::computenode | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp` | Red Hat:enterprise_linux:6::computenode | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-common` | Red Hat:enterprise_linux:6::computenode | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhclient` | Red Hat:enterprise_linux:6::server | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp` | Red Hat:enterprise_linux:6::server | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-common` | Red Hat:enterprise_linux:6::server | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-devel` | Red Hat:enterprise_linux:6::server | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhclient` | Red Hat:enterprise_linux:6::workstation | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp` | Red Hat:enterprise_linux:6::workstation | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-common` | Red Hat:enterprise_linux:6::workstation | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhcp-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 12:4.1.1-53.P1.el6_9.4 | | `dhclient` | Red Hat:enterprise_linux:7::client | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp` | Red Hat:enterprise_linux:7::client | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-common` | Red Hat:enterprise_linux:7::client | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-devel` | Red Hat:enterprise_linux:7::client | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-libs` | Red Hat:enterprise_linux:7::client | All versions | 12:4.2.5-68.el7_5.1 | | `dhclient` | Red Hat:enterprise_linux:7::computenode | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp` | Red Hat:enterprise_linux:7::computenode | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-common` | Red Hat:enterprise_linux:7::computenode | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 12:4.2.5-68.el7_5.1 | | `dhclient` | Red Hat:enterprise_linux:7::server | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp` | Red Hat:enterprise_linux:7::server | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-common` | Red Hat:enterprise_linux:7::server | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-devel` | Red Hat:enterprise_linux:7::server | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp-libs` | Red Hat:enterprise_linux:7::server | All versions | 12:4.2.5-68.el7_5.1 | | `dhclient` | Red Hat:enterprise_linux:7::workstation | All versions | 12:4.2.5-68.el7_5.1 | | `dhcp` | Red Hat:enterprise_linux:7::workstation | All versions | 12:4.2.5-68.el7_5.1 | Products: Fedoraproject Fedora, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation, Redhat Enterprise Virtualization, Redhat Enterprise Virtualization Host. ## How do I fix CVE-2018-1111? Apply the vendor's patch. ## Is CVE-2018-1111 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1111 exists. Public exploit code: - Environment for DynoRoot (CVE-2018-1111) (github_poc): https://github.com/knqyf263/CVE-2018-1111 - CVE-2018-1111 DynoRoot (github_poc): https://github.com/kkirsche/CVE-2018-1111 - DHCP Client Command Injection (DynoRoot) (metasploit) - DynoRoot DHCP Client - Command Injection (exploitdb) - DHCP Client - Command Injection 'DynoRoot' (Metasploit) (exploitdb) - DHCP Client - Command Injection 'DynoRoot' (Metasploit) (exploitdb) ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-1111 and fix it if it is affected. What it is: CVE-2018-1111 is a high-severity command injection vulnerability in Fedoraproject Fedora, published on 17 May 2018. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1111 exists. Affected product: Fedoraproject Fedora. 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-2018-1111/ (Markdown: https://insights.sbomify.com/CVE-2018-1111/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1111 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1111 - OSV: https://osv.dev/vulnerability/CVE-2018-1111 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-1111/ Summaries are generated and may contain mistakes; the official description above is the record.