# CVE-2018-18472: Command injection in n/a

> Remote attackers can execute arbitrary commands as root on WD My Book Live devices via shell metacharacters in the language configuration parameter.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gjqh-4gc9-vchf

## What is CVE-2018-18472?

CVE-2018-18472 is a critical command injection vulnerability in n/a, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Western Digital WD My Book Live and WD My Book Live Duo (all versions) have a root Remote Command Execution bug via shell metacharacters in the /api/1.0/rest/language_configuration language parameter. It can be triggered by anyone who knows the IP address of the affected device, as exploited in the wild in June 2021 for factory reset commands,

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2018-18472?

It affects 1 product.


Products: Westerndigital My Book Live Firmware.

## How do I fix CVE-2018-18472?

No fix has been published for CVE-2018-18472 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-18472 being exploited?

There is no known exploitation of CVE-2018-18472 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-18472 and fix it if it is affected.

What it is: CVE-2018-18472 is a critical command injection vulnerability in n/a, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18472 in the wild and no public exploit code.

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-2018-18472/ (Markdown: https://insights.sbomify.com/CVE-2018-18472/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-18472
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-18472
- OSV: https://osv.dev/vulnerability/CVE-2018-18472

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-18472/
Summaries are generated and may contain mistakes; the official description above is the record.