# CVE-2020-15816: In Western Digital WD Discovery before 4.0.251.0, a malicious application running with standard user permissions could potentially execute c


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3h98-pjm4-888p

## What is CVE-2020-15816?

CVE-2020-15816 is a high-severity vulnerability in n/a, published on 17 Jul 2020. 

### Official description

In Western Digital WD Discovery before 4.0.251.0, a malicious application running with standard user permissions could potentially execute code in the application's process through library injection by using DYLD environment variables.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2020-15816?

It affects 1 product.


Products: Westerndigital Wd Discovery.

## How do I fix CVE-2020-15816?

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

## Is CVE-2020-15816 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12427](https://insights.sbomify.com/CVE-2020-12427/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-29835](https://insights.sbomify.com/CVE-2022-29835/): WD Discovery's Use of Weak Hashing Algorithm for Code Signing (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15816 and fix it if it is affected.

What it is: CVE-2020-15816 is a high-severity vulnerability in n/a, published on 17 Jul 2020. 
Exploitation: There is no known exploitation of CVE-2020-15816 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-2020-15816/ (Markdown: https://insights.sbomify.com/CVE-2020-15816/index.md)
```

## Sources

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

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