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
Medium 5.0
Published
Updated
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)
- Exploited in the wild
- Not known
- Fix
- Available
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 include 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: 1 Exploit-DB entry.
Other vulnerabilities in Wireshark Wireshark
Sources
Also known as GHSA-7ppr-2cvm-q8gq.