# CVE-2022-27534: Memory corruption in Kaspersky Anti-Virus products for home and Kaspersky Endpoint Security

> A bug in the data parsing module allows attackers to execute arbitrary code on Kaspersky antivirus products.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 1 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3jp7-w7p7-xq57

## What is CVE-2022-27534?

CVE-2022-27534 is a critical memory corruption vulnerability in Kaspersky Anti-Virus products for home and Kaspersky Endpoint Security, published on 1 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kaspersky Anti-Virus products for home and Kaspersky Endpoint Security with antivirus databases released before 12 March 2022 had a bug in a data parsing module that potentially allowed an attacker to execute arbitrary code. The fix was delivered automatically. Credits: Georgy Zaytsev (Positive Technologies).

## Which versions are affected by CVE-2022-27534?

It affects 6 products.


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

## How do I fix CVE-2022-27534?

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

## Is CVE-2022-27534 being exploited?

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

## Other vulnerabilities in Kaspersky Anti-Virus products for home and Kaspersky Endpoint Security

- [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)
- [CVE-2019-15685](https://insights.sbomify.com/CVE-2019-15685/): Security feature bypass in Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Total Security, Kaspersky Free Anti-Virus, Kaspersky Small Office Security, Kaspersky Security Cloud (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27534 and fix it if it is affected.

What it is: CVE-2022-27534 is a critical memory corruption vulnerability in Kaspersky Anti-Virus products for home and Kaspersky Endpoint Security, published on 1 Apr 2022. 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-2022-27534 in the wild and no public exploit code.

Affected product: Kaspersky Anti-Virus products for home and Kaspersky Endpoint 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-2022-27534/ (Markdown: https://insights.sbomify.com/CVE-2022-27534/index.md)
```

## Sources

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

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