# CVE-2015-3215: Denial of service in n/a

> Remote attackers can crash Windows guests by sending crafted IP packets with invalid length values to the NetKVM Virtio driver.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4jxc-842p-4w6x, RHSA-2015:1043, RHSA-2015:1044

## What is CVE-2015-3215?

CVE-2015-3215 is a high-severity denial of service vulnerability in n/a, published on 26 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The NetKVM Windows Virtio driver allows remote attackers to cause a denial of service (guest crash) via a crafted length value in an IP packet, as demonstrated by a value that does not account for the size of the IP options.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2015-3215?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `virtio-win` | Red Hat:rhel_extras:6 | All versions | 0:1.7.4-1.el6_6 |
| `virtio-win` | Red Hat:rhel_extras:7 | All versions | 0:1.7.4-1.el7 |

Products: Redhat Virtio-Win.

## How do I fix CVE-2015-3215?

Apply the vendor's patch.

## Is CVE-2015-3215 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3215 and fix it if it is affected.

What it is: CVE-2015-3215 is a high-severity denial of service vulnerability in n/a, published on 26 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3215 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-2015-3215/ (Markdown: https://insights.sbomify.com/CVE-2015-3215/index.md)
```

## Sources

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

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