# CVE-2019-8285: Memory corruption in Kaspersky Lab Antivirus Engine

> A heap-based buffer overflow in the Kaspersky Antivirus Engine allows attackers to execute arbitrary code on the host system.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-62gg-g3mg-cmc5

## What is CVE-2019-8285?

CVE-2019-8285 is a high-severity memory corruption vulnerability in Kaspersky Lab Antivirus Engine, published on 8 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kaspersky Lab Antivirus Engine version before 04.apr.2019 has a heap-based buffer overflow vulnerability that potentially allow arbitrary code execution

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

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

It affects 1 product.


Products: Kaspersky Antivirus Engine.

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

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

## Is CVE-2019-8285 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-8285 is a high-severity memory corruption vulnerability in Kaspersky Lab Antivirus Engine, published on 8 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-8285 in the wild and no public exploit code.

Affected product: Kaspersky Lab Antivirus Engine. 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-8285/ (Markdown: https://insights.sbomify.com/CVE-2019-8285/index.md)
```

## Sources

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

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