# CVE-2020-15596: Path traversal in n/a

> Attackers can disclose sensitive paths via a fake DLL file in the ALPS touchpad driver, affecting Dell, HP, and Lenovo laptops.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xp9g-2jr8-5wm3

## What is CVE-2020-15596?

CVE-2020-15596 is a medium-severity path traversal vulnerability in n/a, published on 12 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ALPS ALPINE touchpad driver before 8.2206.1717.634, as used on various Dell, HP, and Lenovo laptops, allows attackers to conduct Path Disclosure attacks via a "fake" DLL file.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 14 products.


Products: Hp Elite X2 1012 G1 Firmware, Hp Elite X2 1012 G2 Firmware, Hp Elitebook 1030 G1 Firmware, Hp Elitebook 1040 G4 Firmware, Hp Elitebook Folio 1040 G3 Firmware, Hp Elitebook Folio G1 Firmware, Hp Elitebook Revolve 810 G2 Firmware, Hp Elitebook Revolve 810 G3 Firmware, Hp Elitebook X360 1020 G2 Firmware, Hp Elitebook X360 1030 G2 Firmware, Hp Pro X2 612 G2 Firmware, Hp Zbook Studio G3 Firmware, Hp Zbook Studio G4 Firmware, Hp Zbook X2 G4 Firmware.

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

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

## Is CVE-2020-15596 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-15596 is a medium-severity path traversal vulnerability in n/a, published on 12 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-15596 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-15596/ (Markdown: https://insights.sbomify.com/CVE-2020-15596/index.md)
```

## Sources

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

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