# CVE-2018-17153: Auth bypass in n/a

> Unauthenticated attackers can bypass authentication to gain admin privileges and full control of Western Digital My Cloud devices.

- **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:** 18 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-22xm-47fv-r79q

## What is CVE-2018-17153?

CVE-2018-17153 is a critical authentication bypass vulnerability in n/a, published on 18 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was discovered that the Western Digital My Cloud device before 2.30.196 is affected by an authentication bypass vulnerability. An unauthenticated attacker can exploit this vulnerability to authenticate as an admin user without needing to provide a password, thereby gaining full control of the device. (Whenever an admin logs into My Cloud, a server-side session is created that is bound to the user's IP address. After the session is created, it is possible to call authenticated CGI modules by sending the cookie username=admin in the HTTP request. The invoked CGI will check if a valid session is present and bound to the user's IP address.) It was found that it is possible for an unauthenticated attacker to create a valid session without a login. The network_mgr.cgi CGI module contains a command called "cgi_get_ipv6" that starts an admin session -- tied to the IP address of the user making the request -- if the additional parameter "flag" with the value "1" is provided. Subsequent invocation of commands that would normally require admin privileges now succeed if an attacker sets the username=admin cookie.

Weakness: CWE-287 (Improper Authentication)

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

It affects 12 products.


Products: Western Digital My Cloud Dl2100, Western Digital My Cloud Dl4100 Firmware, Western Digital My Cloud Ex2100 Firmware, Western Digital My Cloud Ex2 Firmware, Western Digital My Cloud Ex2 Ultra Firmware, Western Digital My Cloud Ex4100, Western Digital My Cloud Ex4 Firmware, Western Digital My Cloud Mirror Firmware, Western Digital My Cloud Mirror Gen 2 Firmware, Western Digital My Cloud Pr2100 Firmware, Western Digital My Cloud Pr4100, Western Digital My Cloud Wdbctl0020hwt Firmware.

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

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

## Is CVE-2018-17153 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-17153 exists.

Public exploit code:

- Western Digital MyCloud unauthenticated command injection (metasploit)
- Western Digital MyCloud NAS - Authentication Bypass (nuclei): http/cves/2018/CVE-2018-17153.yaml

## Other vulnerabilities in n/a

- [CVE-2019-9951](https://insights.sbomify.com/CVE-2019-9951/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17153 is a critical authentication bypass vulnerability in n/a, published on 18 Sep 2018. 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-2018-17153 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-2018-17153/ (Markdown: https://insights.sbomify.com/CVE-2018-17153/index.md)
```

## Sources

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

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