# CVE-2020-8096: Untrusted Search Path Vulnerability in High-Level Antimalware SDK

> An attacker can execute arbitrary code by placing a malicious DLL in the search path of the Bitdefender High-Level Antimalware SDK.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **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:** 7 Apr 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-frjx-44vq-w3hv

## What is CVE-2020-8096?

CVE-2020-8096 is a medium-severity vulnerability in Bitdefender High-Level Antimalware SDK for Windows, published on 7 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted Search Path vulnerability in Bitdefender High-Level Antimalware SDK for Windows allows an attacker to load third party code from a DLL library in the search path. This issue affects: Bitdefender High-Level Antimalware SDK for Windows versions prior to 3.0.1.204 .

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


Products: Bitdefender Antimalware Software Development Kit.

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

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

## Is CVE-2020-8096 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8096 is a medium-severity vulnerability in Bitdefender High-Level Antimalware SDK for Windows, published on 7 Apr 2020. 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-2020-8096 in the wild and no public exploit code.

Affected product: Bitdefender High-Level Antimalware SDK for Windows. 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-8096/ (Markdown: https://insights.sbomify.com/CVE-2020-8096/index.md)
```

## Sources

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

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