CVE-2009-0778

Public Exploit

Description

The icmp_send function in net/ipv4/icmp.c in the Linux kernel before 2.6.25, when configured as a router with a REJECT route, does not properly manage the Protocol Independent Destination Cache (aka DST) in some situations involving transmission of an ICMP Host Unreachable message, which allows remote attackers to cause a denial of service (connectivity outage) by sending a large series of packets to many destination IP addresses within this REJECT route, related to an "rt_cache leak."

7.1

CVSS

Severity: High

CVSS 2.0 •

EPSS 2.06% Top 20%

Vendor Advisory redhat.com

Affected: n/a n/a

References

Link	Tags
http://www.redhat.com/support/errata/RHSA-2009-0326.html	vendor advisory broken link
http://secunia.com/advisories/37471	third party advisory broken link
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=7c0ecc4c4f8fd90988aab8a95297b9c0038b6160
http://www.vmware.com/security/advisories/VMSA-2009-0016.html	third party advisory
http://secunia.com/advisories/33758	third party advisory broken link
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10215	vdb entry third party advisory signature
http://www.securityfocus.com/archive/1/507985/100/0/threaded	mailing list vdb entry third party advisory
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A7867	vdb entry third party advisory signature
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.25	broken link
http://openwall.com/lists/oss-security/2009/03/11/2	third party advisory mailing list
http://www.securitytracker.com/id?1021958	vdb entry third party advisory
https://exchange.xforce.ibmcloud.com/vulnerabilities/49199	vdb entry third party advisory
https://bugzilla.redhat.com/show_bug.cgi?id=485163	issue tracking exploit third party advisory
http://www.vupen.com/english/advisories/2009/3316	vdb entry broken link
http://www.securityfocus.com/bid/34084	vdb entry third party advisory

Frequently Asked Questions

What is the severity of CVE-2009-0778?: CVE-2009-0778 has been scored as a high severity vulnerability.
How to fix CVE-2009-0778?: To fix CVE-2009-0778, 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-0778 being actively exploited in the wild?: It is possible that CVE-2009-0778 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~2% probability that this vulnerability will be exploited by malicious actors in the next 30 days.