CVE-2009-2561 json
Unspecified vulnerability in the sFlow dissector in Wireshark 1.2.0 allows remote attackers to cause a denial of service (CPU and memory co…
published 2009-07-21 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-2556
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the sFlow dissector in Wireshark 1.2.0 allows remote attackers to cause a denial of service (CPU and memory consumption) via unspecified vectors.
Patch / fix
- wireshark Debian 14, Debian 13, Debian 12 1.2.1-1
debian advisories DEBIAN-CVE-2009-2561
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2009-2561 updated cvss 4.3
Wireshark: Dos (excessive CPU and memory use) via large amount of tree items in the sFlow dissector
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.95% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
References
-
wireshark.org
/security/wnpa-sec-2009-04.html
patch, vendor-advisory
-
vupen.com
/english/advisories/2009/1970
vdb-entry, patch, vendor-advisory
-
securityfocus.com
/bid/35748
vdb-entry, patch
-
secunia.com
/advisories/35884
third-party-advisory, vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A5795
vdb-entry, signature
Sources
- CVE List CVE-2009-2561
- NVD CVE-2009-2561
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.