# CVE-2019-8286: Information disclosure in Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Total Security

> An attacker can disclose the unique Product ID by forcing a victim to visit a specially crafted webpage, affecting Kaspersky security products.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w896-5884-6r99

## What is CVE-2019-8286?

CVE-2019-8286 is a medium-severity vulnerability in Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Total Security, published on 18 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Information Disclosure in Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Total Security versions up to 2019 could potentially disclose unique Product ID by forcing victim to visit a specially crafted webpage (for example, via clicking phishing link). Vulnerability has CVSS v3.0 base score 2.6

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 5 products.


Products: Kaspersky Anti-Virus, Kaspersky Free Anti-Virus, Kaspersky Internet Security, Kaspersky Small Office Security, Kaspersky Total Security.

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

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

## Is CVE-2019-8286 being exploited?

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

## Other vulnerabilities in Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Total Security

- [CVE-2022-27534](https://insights.sbomify.com/CVE-2022-27534/): Memory corruption in Kaspersky Anti-Virus products for home and Kaspersky Endpoint Security (critical 9.8)
- [CVE-2019-15687](https://insights.sbomify.com/CVE-2019-15687/): Information disclosure in Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Total Security, Kaspersky Free Anti-Virus, Kaspersky Small Office Security, Kaspersky Security Cloud (medium 6.5)
- [CVE-2019-15688](https://insights.sbomify.com/CVE-2019-15688/): Open redirect in Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Total Security, Kaspersky Free Anti-Virus, Kaspersky Small Office Security, Kaspersky Security Cloud (medium 6.1)
- [CVE-2021-27223](https://insights.sbomify.com/CVE-2021-27223/): Denial of service in Kaspersky Anti-Virus products for home and Kaspersky Endpoint Security (medium 5.5)
- [CVE-2016-4329](https://insights.sbomify.com/CVE-2016-4329/): Denial of service in Total Security (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-8286 is a medium-severity vulnerability in Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Total Security, published on 18 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-8286 in the wild and no public exploit code.

Affected product: Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Total Security. 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-8286/ (Markdown: https://insights.sbomify.com/CVE-2019-8286/index.md)
```

## Sources

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

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