# CVE-2017-9264: Memory corruption in n/a

> Remote attackers can cause a denial of service in Open vSwitch by sending malformed TCP, UDP, or IPv6 packets that trigger a buffer over-read.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 29 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-9264, GHSA-r4pw-w7qg-248f

## What is CVE-2017-9264?

CVE-2017-9264 is a critical memory corruption vulnerability in n/a, published on 29 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In lib/conntrack.c in the firewall implementation in Open vSwitch (OvS) 2.6.1, there is a buffer over-read while parsing malformed TCP, UDP, and IPv6 packets in the functions `extract_l3_ipv6`, `extract_l4_tcp`, and `extract_l4_udp` that can be triggered remotely.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Openvswitch Openvswitch.

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

Upgrade to a fixed version.

## Is CVE-2017-9264 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9265](https://insights.sbomify.com/CVE-2017-9265/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-2074](https://insights.sbomify.com/CVE-2016-2074/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-10377](https://insights.sbomify.com/CVE-2016-10377/): Integer overflow in n/a (high 8.8)
- [CVE-2024-22563](https://insights.sbomify.com/CVE-2024-22563/): Denial of service in n/a (high 7.5)
- [CVE-2023-5366](https://insights.sbomify.com/CVE-2023-5366/): Openvswitch don't match packets on nd_target field (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9264 is a critical memory corruption vulnerability in n/a, published on 29 May 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-2017-9264 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-9264/ (Markdown: https://insights.sbomify.com/CVE-2017-9264/index.md)
```

## Sources

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

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