# CVE-2018-5410: Dokan file system driver contains a stack-based buffer overflow

> A stack-based buffer overflow in the Dokan file system driver allows attackers to execute arbitrary code with kernel privileges via crafted input.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-353c-4p9g-7m63

## What is CVE-2018-5410?

CVE-2018-5410 is a high-severity memory corruption vulnerability in Dokan Open Source File System, published on 7 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dokan, versions between 1.0.0.5000 and 1.2.0.1000, are vulnerable to a stack-based buffer overflow in the dokan1.sys driver. An attacker can create a device handle to the system driver and send arbitrary input that will trigger the vulnerability. This vulnerability was introduced in the 1.0.0.5000 version update.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Dokan-Dev Dokany.

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

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

## Is CVE-2018-5410 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-5410 exists.

Public exploit code:

- Dokany 1.2.0.1000 - Stack-Based Buffer Overflow Privilege Escalation (exploitdb)
- Dokany 1.2.0.1000 - Stack-Based Buffer Overflow Privilege Escalation (exploitdb)

## Other vulnerabilities in Dokan Open Source File System

- [CVE-2018-20029](https://insights.sbomify.com/CVE-2018-20029/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-5410 is a high-severity memory corruption vulnerability in Dokan Open Source File System, published on 7 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-5410 exists.

Affected product: Dokan Open Source File System. 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-5410/ (Markdown: https://insights.sbomify.com/CVE-2018-5410/index.md)
```

## Sources

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

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