# CVE-2018-20404: Denial of service in n/a

> A local attacker can cause a system hang or Blue Screen of Death in the VIA EPIA-E900 SmartETK driver via a specific IOCTL call.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 26 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mr4r-rgr7-6hqw

## What is CVE-2018-20404?

CVE-2018-20404 is a high-severity denial of service vulnerability in n/a, published on 26 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ETK_E900.sys, a SmartETK driver for VIA Technologies EPIA-E900 system board, is vulnerable to denial of service attack via IOCTL 0x9C402048, which calls memmove and constantly fails on an arbitrary (uncontrollable) address, resulting in an eternal hang or a BSoD.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Viatech Epia-E900 Firmware.

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

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

## Is CVE-2018-20404 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20404 is a high-severity denial of service vulnerability in n/a, published on 26 Dec 2018. 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-2018-20404 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-2018-20404/ (Markdown: https://insights.sbomify.com/CVE-2018-20404/index.md)
```

## Sources

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

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