# CVE-2019-13156: Memory corruption in NDrive

> A stack-based buffer overflow in the NDrive kernel driver allows attackers to cause a denial of service via IOCTL requests.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 3 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2pqp-qqmg-62w8

## What is CVE-2019-13156?

CVE-2019-13156 is a high-severity memory corruption vulnerability in NAVER Corporation NDrive, published on 3 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NDrive(1.2.2).sys in Naver Cloud Explorer has a stack-based buffer overflow, which allows attackers to cause a denial of service when reading data from IOCTL handle.

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

## Which versions are affected by CVE-2019-13156?

It affects 1 product.


Products: Naver Cloud Explorer.

## How do I fix CVE-2019-13156?

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

## Is CVE-2019-13156 being exploited?

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

## Other vulnerabilities in NAVER Corporation NDrive

- [CVE-2020-9752](https://insights.sbomify.com/CVE-2020-9752/): Path traversal in Naver Cloud Explorer (critical 9.8)
- [CVE-2020-9751](https://insights.sbomify.com/CVE-2020-9751/): Code injection in Naver Cloud Explorer (critical 9.1)
- [CVE-2022-24077](https://insights.sbomify.com/CVE-2022-24077/): Privilege escalation in NAVER Cloud Explorer Beta (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13156 and fix it if it is affected.

What it is: CVE-2019-13156 is a high-severity memory corruption vulnerability in NAVER Corporation NDrive, published on 3 Sep 2019. 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-2019-13156 in the wild and no public exploit code.

Affected product: NAVER Corporation NDrive. 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-2019-13156/ (Markdown: https://insights.sbomify.com/CVE-2019-13156/index.md)
```

## Sources

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

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