# CVE-2020-15293: Memory corruption in Bitdefender Hypervisor Introspection (VA-9336)

> Insufficient input validation in Bitdefender Hypervisor Introspection allows attackers to cause memory corruption and denial of service.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **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:** 17 Dec 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2jrp-2x8m-mgrv

## What is CVE-2020-15293?

CVE-2020-15293 is a medium-severity memory corruption vulnerability in Bitdefender Hypervisor Introspection, published on 17 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption in IntLixCrashDumpDmesg, IntLixTaskFetchCmdLine, IntLixFileReadDentry and IntLixFileGetPath due to insufficient guest-data input validation may lead to denial of service conditions.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Bitdefender Hypervisor Introspection.

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

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

## Is CVE-2020-15293 being exploited?

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

## Other vulnerabilities in Bitdefender Hypervisor Introspection

- [CVE-2020-15294](https://insights.sbomify.com/CVE-2020-15294/): Race condition in Hypervisor Introspection (high 7.8)
- [CVE-2020-15292](https://insights.sbomify.com/CVE-2020-15292/): Lack of validation on data read from guest memory in Bitdefender HVI (VA-9333) (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-15293 is a medium-severity memory corruption vulnerability in Bitdefender Hypervisor Introspection, published on 17 Dec 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-15293 in the wild and no public exploit code.

Affected product: Bitdefender Hypervisor Introspection. 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-15293/ (Markdown: https://insights.sbomify.com/CVE-2020-15293/index.md)
```

## Sources

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

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