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

> An attacker can exploit path traversal during OBIS code downloads to place malicious files in autorun directories or the application folder, achieving code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 25 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8c45-q5hv-c92h

## What is CVE-2020-8810?

CVE-2020-8810 is a high-severity path traversal vulnerability in n/a, published on 25 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Gurux GXDLMS Director through 8.5.1905.1301. When downloading OBIS codes, it does not verify that the downloaded files are actual OBIS codes and doesn't check for path traversal. This allows the attacker exploiting CVE-2020-8809 to send executable files and place them in an autorun directory, or to place DLLs inside the existing GXDLMS Director installation (run on next execution of GXDLMS Director). This can be used to achieve code execution even if the user doesn't have any add-ins installed.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Gurux Device Language Message Specification Director.

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

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

## Is CVE-2020-8810 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-8809](https://insights.sbomify.com/CVE-2020-8809/): Supply chain in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8810 is a high-severity path traversal vulnerability in n/a, published on 25 Feb 2020. 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-2020-8810 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-8810/ (Markdown: https://insights.sbomify.com/CVE-2020-8810/index.md)
```

## Sources

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

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