# CVE-2020-28950: Privilege escalation in Kaspersky Anti-Ransomware Tool

> An attacker can elevate privileges via DLL hijacking during the installation of Kaspersky Anti-Ransomware Tool.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4h59-pfrp-mwp4

## What is CVE-2020-28950?

CVE-2020-28950 is a high-severity vulnerability in Kaspersky Anti-Ransomware Tool, published on 4 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The installer of Kaspersky Anti-Ransomware Tool (KART) prior to KART 4.0 Patch C was vulnerable to a DLL hijacking attack that allowed an attacker to elevate privileges during installation process.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2020-28950?

It affects 1 product.


Products: Kaspersky Anti-Ransomware Tool.

## How do I fix CVE-2020-28950?

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

## Is CVE-2020-28950 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-28950 and fix it if it is affected.

What it is: CVE-2020-28950 is a high-severity vulnerability in Kaspersky Anti-Ransomware Tool, published on 4 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-28950 in the wild and no public exploit code.

Affected product: Kaspersky Anti-Ransomware Tool. 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-2020-28950/ (Markdown: https://insights.sbomify.com/CVE-2020-28950/index.md)
```

## Sources

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

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