# CVE-2020-15479: Memory corruption in n/a

> A buffer overflow in PassMark kernel drivers allows local attackers to execute arbitrary code in Ring-0 and escalate privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/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:** 7 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-chrj-qx57-jxqj

## What is CVE-2020-15479?

CVE-2020-15479 is a high-severity memory corruption vulnerability in n/a, published on 7 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in PassMark BurnInTest through 9.1, OSForensics through 7.1, and PerformanceTest through 10. The driver's IOCTL request handler attempts to copy the input buffer onto the stack without checking its size and can cause a buffer overflow. This could lead to arbitrary Ring-0 code execution and escalation of privileges. This affects DirectIo32.sys and DirectIo64.sys.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 3 products.


Products: Passmark Burnintest, Passmark Osforensics, Passmark Performancetest.

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

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

## Is CVE-2020-15479 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15480](https://insights.sbomify.com/CVE-2020-15480/): Privilege escalation in n/a (high 8.8)
- [CVE-2020-15481](https://insights.sbomify.com/CVE-2020-15481/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-15479 is a high-severity memory corruption vulnerability in n/a, published on 7 Aug 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-15479 in the wild and no public exploit code.

Affected product: n/a. 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-15479/ (Markdown: https://insights.sbomify.com/CVE-2020-15479/index.md)
```

## Sources

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

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