# CVE-2023-6175: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') in Wireshark

> Attackers can cause a denial of service in Wireshark by providing a crafted capture file that triggers a buffer overflow in the NetScreen parser.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Mar 2024
- **Updated:** 27 Mar 2026
- **Also known as:** AZL-42527, AZL-42552, DEBIAN-CVE-2023-6175, GHSA-r8r7-4wvf-px33, OESA-2023-1847, SUSE-SU-2023:4938-1, UBUNTU-CVE-2023-6175

## What is CVE-2023-6175?

CVE-2023-6175 is a high-severity memory corruption vulnerability in Wireshark Wireshark, published on 26 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

NetScreen file parser crash in Wireshark 4.0.0 to 4.0.10 and 3.6.0 to 3.6.18 allows denial of service via crafted capture file

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

## Which versions are affected by CVE-2023-6175?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wireshark` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 3.6.19-150000.3.106.1 |
| `wireshark` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 3.6.19-150000.3.106.1 |
| `wireshark` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP4 | All versions | 3.6.19-150000.3.106.1 |
| `wireshark` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 3.6.19-150000.3.106.1 |
| `wireshark` | openSUSE:Leap 15.4 | All versions | 3.6.19-150000.3.106.1 |
| `wireshark` | openSUSE:Leap 15.5 | All versions | 3.6.19-150000.3.106.1 |

Products: Wireshark Wireshark.

## How do I fix CVE-2023-6175?

Upgrade to a fixed version.

## Is CVE-2023-6175 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6175 exists.

## Other vulnerabilities in Wireshark Wireshark

- [CVE-2011-0444](https://insights.sbomify.com/CVE-2011-0444/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2994](https://insights.sbomify.com/CVE-2010-2994/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2995](https://insights.sbomify.com/CVE-2010-2995/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1266](https://insights.sbomify.com/CVE-2009-1266/): Other in n/a (critical 10.0)
- [CVE-2009-1210](https://insights.sbomify.com/CVE-2009-1210/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6175 and fix it if it is affected.

What it is: CVE-2023-6175 is a high-severity memory corruption vulnerability in Wireshark Wireshark, published on 26 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6175 exists.

Affected product: Wireshark Wireshark. 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-2023-6175/ (Markdown: https://insights.sbomify.com/CVE-2023-6175/index.md)
```

## Sources

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

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