# CVE-2018-19650: Memory corruption in n/a

> Local attackers can exploit a kernel stack buffer overflow in the Antiy-AVL ATool driver to execute arbitrary code and escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 5 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w3mh-hj36-4cjx

## What is CVE-2018-19650?

CVE-2018-19650 is a high-severity memory corruption vulnerability in n/a, published on 5 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Local attackers can trigger a stack-based buffer overflow on vulnerable installations of Antiy-AVL ATool security management v1.0.0.22. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the processing of IOCTL 0x80002000 by the IRPFile.sys Antiy-AVL ATool kernel driver. The bug is caused by failure to properly validate the length of the user-supplied data, which results in a kernel stack buffer overflow. An attacker can leverage this vulnerability to execute arbitrary code in the context of the kernel, which could lead to privilege escalation and a failed exploit could lead to denial of service.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Antiy Anti Virus Lab Atool.

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

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

## Is CVE-2018-19650 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-20331](https://insights.sbomify.com/CVE-2018-20331/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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