# CVE-2017-8339: Denial of service in n/a

> Local attackers can cause a Blue Screen of Death in Panda Free Antivirus by sending a crafted request to the PSKMAD.sys driver.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 30 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xm42-x3fj-82gw

## What is CVE-2017-8339?

CVE-2017-8339 is a medium-severity denial of service vulnerability in n/a, published on 30 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PSKMAD.sys in Panda Free Antivirus 18.0 allows local users to cause a denial of service (BSoD) via a crafted DeviceIoControl request to \\.\PSMEMDriver.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-8339?

It affects 1 product.


Products: Watchguard Panda Antivirus.

## How do I fix CVE-2017-8339?

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

## Is CVE-2017-8339 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-34998](https://insights.sbomify.com/CVE-2021-34998/): Privilege escalation in Free Antivirus (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8339 and fix it if it is affected.

What it is: CVE-2017-8339 is a medium-severity denial of service vulnerability in n/a, published on 30 Apr 2017. 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-2017-8339 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-2017-8339/ (Markdown: https://insights.sbomify.com/CVE-2017-8339/index.md)
```

## Sources

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

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