CVE-2006-5276

Public Exploit

Description

Stack-based buffer overflow in the DCE/RPC preprocessor in Snort before 2.6.1.3, and 2.7 before beta 2; and Sourcefire Intrusion Sensor; allows remote attackers to execute arbitrary code via crafted SMB traffic.

10.0

CVSS

Severity: Critical

CVSS 2.0 •

EPSS 87.70% Top 5%

Vendor Advisory gentoo.org Vendor Advisory fedoranews.org Vendor Advisory iss.net Vendor Advisory snort.org

Affected: n/a n/a

References

Link	Tags
http://www.us-cert.gov/cas/techalerts/TA07-050A.html	third party advisory us government resource
http://www.kb.cert.org/vuls/id/196240	third party advisory us government resource
http://www116.nortelnetworks.com/pub/repository/CLARIFY/DOCUMENT/2007/08/021923-01.pdf
http://security.gentoo.org/glsa/glsa-200703-01.xml	vendor advisory
http://secunia.com/advisories/26746	third party advisory
http://www.securityfocus.com/archive/1/461810/100/0/threaded	mailing list
http://secunia.com/advisories/24190	third party advisory
http://www.snort.org/docs/advisory-2007-02-19.html	vendor advisory
http://secunia.com/advisories/24239	third party advisory
http://secunia.com/advisories/24272	third party advisory
http://www.vupen.com/english/advisories/2007/0656	vdb entry
https://exchange.xforce.ibmcloud.com/vulnerabilities/31275	vdb entry
http://fedoranews.org/updates/FEDORA-2007-206.shtml	vendor advisory
http://www.vupen.com/english/advisories/2007/0668	vdb entry
http://www.osvdb.org/32094	vdb entry
http://secunia.com/advisories/24235	third party advisory
http://www.securitytracker.com/id?1017670	vdb entry
http://secunia.com/advisories/24240	third party advisory
http://iss.net/threats/257.html	third party advisory vendor advisory
http://www.securityfocus.com/bid/22616	vdb entry
http://www130.nortelnetworks.com/go/main.jsp?cscat=BLTNDETAIL&DocumentOID=540173
https://www.exploit-db.com/exploits/3362	exploit
https://bugzilla.redhat.com/show_bug.cgi?id=229265
http://www.securitytracker.com/id?1017669	vdb entry

Frequently Asked Questions

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