# CVE-2020-15009: AsusScreenXpertServicec.exe and ScreenXpertUpgradeServiceManager.exe in ScreenPad2_Upgrade_Tool.msi V1.0.3 for ASUS PCs with ScreenPad 1.0 (


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wc48-v74h-3jcf

## What is CVE-2020-15009?

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

### Official description

AsusScreenXpertServicec.exe and ScreenXpertUpgradeServiceManager.exe in ScreenPad2_Upgrade_Tool.msi V1.0.3 for ASUS PCs with ScreenPad 1.0 (UX450FDX, UX550GDX and UX550GEX) could lead to unsigned code execution with no additional restrictions when a user puts an application at a particular path with a particular file name.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


Products: Asus Screenpad2 Upgrade Tool.

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

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

## Is CVE-2020-15009 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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