CVE-2009-2560

Description

Multiple unspecified vulnerabilities in Wireshark 1.2.0 allow remote attackers to cause a denial of service (application crash) via a file that records a malformed packet trace and is processed by the (1) Bluetooth L2CAP, (2) RADIUS, or (3) MIOP dissector. NOTE: it was later reported that the RADIUS issue also affects 0.10.13 through 1.0.9.

5.0

CVSS

Severity: Medium

CVSS 2.0 •

EPSS 2.69% Top 15%

Vendor Advisory mandriva.com Vendor Advisory debian.org Vendor Advisory secunia.com Vendor Advisory secunia.com Vendor Advisory secunia.com Vendor Advisory secunia.com Vendor Advisory vupen.com Vendor Advisory vupen.com Vendor Advisory wireshark.org

Affected: n/a n/a

References

Link	Tags
http://www.securityfocus.com/bid/36846	vdb entry
http://www.mandriva.com/security/advisories?name=MDVSA-2009:194	vendor advisory
http://www.wireshark.org/security/wnpa-sec-2009-04.html	patch vendor advisory
http://secunia.com/advisories/37477	third party advisory vendor advisory
http://www.vupen.com/english/advisories/2009/3061	vdb entry vendor advisory
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10403	vdb entry signature
http://www.openwall.com/lists/oss-security/2009/07/22/2	mailing list
http://www.vupen.com/english/advisories/2009/1970	vdb entry vendor advisory
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6416	vdb entry signature
https://exchange.xforce.ibmcloud.com/vulnerabilities/54019	vdb entry
http://www.wireshark.org/docs/relnotes/wireshark-1.0.10.html
http://www.securityfocus.com/bid/35748	vdb entry patch
http://secunia.com/advisories/35884	third party advisory vendor advisory
http://secunia.com/advisories/37409	third party advisory vendor advisory
http://www.wireshark.org/security/wnpa-sec-2009-08.html
http://www.debian.org/security/2009/dsa-1942	vendor advisory
http://secunia.com/advisories/37175	third party advisory vendor advisory

Frequently Asked Questions

What is the severity of CVE-2009-2560?: CVE-2009-2560 has been scored as a medium severity vulnerability.
How to fix CVE-2009-2560?: To fix CVE-2009-2560, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2009-2560 being actively exploited in the wild?: It is possible that CVE-2009-2560 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~3% probability that this vulnerability will be exploited by malicious actors in the next 30 days.