# CVE-2014-7817: Command injection in n/a > Attackers can execute arbitrary commands via the wordexp function in glibc due to missing enforcement of the WRDE_NOCMD flag. - **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Not stated - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Nov 2014 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2014-7817, GHSA-47cv-pfmg-555j, MGASA-2014-0496, RHSA-2014:2023, UBUNTU-CVE-2014-7817 ## What is CVE-2014-7817? CVE-2014-7817 is a medium-severity command injection vulnerability in Canonical Ubuntu Linux, published on 24 Nov 2014. ### Official description The wordexp function in GNU C Library (aka glibc) 2.21 does not enforce the WRDE_NOCMD flag, which allows context-dependent attackers to execute arbitrary commands, as demonstrated by input containing "$((`...`))". Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2014-7817? It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `glibc` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-55.el7_0.3 | | `glibc-common` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-55.el7_0.3 | | `glibc-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-55.el7_0.3 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-55.el7_0.3 | | `glibc-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-55.el7_0.3 | | `glibc-headers` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-55.el7_0.3 | | `glibc-static` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-55.el7_0.3 | | `glibc-utils` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-55.el7_0.3 | | `nscd` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-55.el7_0.3 | | `glibc` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-55.el7_0.3 | | `glibc-common` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-55.el7_0.3 | | `glibc-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-55.el7_0.3 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-55.el7_0.3 | | `glibc-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-55.el7_0.3 | | `glibc-headers` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-55.el7_0.3 | | `glibc-static` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-55.el7_0.3 | | `glibc-utils` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-55.el7_0.3 | | `nscd` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-55.el7_0.3 | | `glibc` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-55.el7_0.3 | | `glibc-common` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-55.el7_0.3 | | `glibc-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-55.el7_0.3 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-55.el7_0.3 | | `glibc-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-55.el7_0.3 | | `glibc-headers` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-55.el7_0.3 | | `glibc-static` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-55.el7_0.3 | | `glibc-utils` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-55.el7_0.3 | | `nscd` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-55.el7_0.3 | | `glibc` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-55.el7_0.3 | | `glibc-common` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-55.el7_0.3 | | `glibc-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-55.el7_0.3 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-55.el7_0.3 | | `glibc-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-55.el7_0.3 | | `glibc-headers` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-55.el7_0.3 | | `glibc-static` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-55.el7_0.3 | | `glibc-utils` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-55.el7_0.3 | | `nscd` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-55.el7_0.3 | Products: Canonical Ubuntu Linux, Debian Debian Linux, Gnu Glibc, Opensuse Opensuse. ## How do I fix CVE-2014-7817? Apply the vendor's patch. ## Is CVE-2014-7817 being exploited? There is no known exploitation of CVE-2014-7817 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2014-7817 and fix it if it is affected. What it is: CVE-2014-7817 is a medium-severity command injection vulnerability in Canonical Ubuntu Linux, published on 24 Nov 2014. Exploitation: There is no known exploitation of CVE-2014-7817 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. 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-2014-7817/ (Markdown: https://insights.sbomify.com/CVE-2014-7817/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2014-7817 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-7817 - OSV: https://osv.dev/vulnerability/CVE-2014-7817 --- From sbomify Insights: https://insights.sbomify.com/CVE-2014-7817/ Summaries are generated and may contain mistakes; the official description above is the record.