# CVE-2009-3243: Unspecified vulnerability in the TLS dissector in Wireshark 1.2.0 and 1.2.1, when running on Windows, allows remote attackers to cause a den


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7ppr-2cvm-q8gq

## What is CVE-2009-3243?

CVE-2009-3243 is a medium-severity vulnerability in Wireshark Wireshark, published on 18 Sep 2009. 

### Official description

Unspecified vulnerability in the TLS dissector in Wireshark 1.2.0 and 1.2.1, when running on Windows, allows remote attackers to cause a denial of service (application crash) via unknown vectors related to TLS 1.2 conversations.

## Which versions are affected by CVE-2009-3243?

It affects 1 product.


Products: Wireshark Wireshark.

## How do I fix CVE-2009-3243?

Upgrade to a fixed version.

## Is CVE-2009-3243 being exploited?

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

Public exploit code:

- Wireshark 1.2.1 - TLS Dissector 1.2 Conversation Handling Remote Denial of Service (exploitdb)

## 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-2009-3243 and fix it if it is affected.

What it is: CVE-2009-3243 is a medium-severity vulnerability in Wireshark Wireshark, published on 18 Sep 2009. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3243 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-2009-3243/ (Markdown: https://insights.sbomify.com/CVE-2009-3243/index.md)
```

## Sources

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

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