{"vuid":"VU#175500","idnumber":"175500","name":"Snort Back Orifice preprocessor buffer overflow","keywords":["Snort","Back Orifice preprocessor","buffer overflow","intrusion detection system","remote code execution","UDP"],"overview":"A buffer overflow exists in the Snort Back Orifice preprocessor that may allow a remote, unauthenticated attacker to execute arbitrary code, possibly with elevated privileges.","clean_desc":"Snort is an open-source intrusion detection system (IDS). A lack of validation on attacker-controlled data may allow a buffer overflow to occur in the in Snort Back Orifice preprocessor. A remote, unauthenticated attacker may be able to trigger the buffer overflow by sending a specially crafted Back Orifice ping to a vulnerable Snort installation. To exploit this vulnerability, an attacker does not need to send packets directly to the Snort sensor. It is sufficient to send packets to any of the hosts on the network monitored by Snort.","impact":"A remote attacker can execute arbitrary code with the privileges of the Snort process, typically root or SYSTEM.","resolution":"Update This issue has been addressed in Snort version 2.4.3.","workarounds":"Disable Snort Back Orifice preprocessor Disabling the Snort Back Orifice preprocessor will mitigate this vulnerability. However, without the Snort preprocessor, the Snort sensor will not detect or prevent Back Orifice traffic. Snort suggests the following steps to disable the Back Orifice preprocessor: The Back Orifice preprocessor can be disabled by commenting out the line \"preprocessor bo\" in snort.conf. This can be done in any text editor using the following procedure: 1. Locate the line \"preprocessor bo\"\n2. Comment out this line by preceding it with a hash (#). The new line will look like \"#preprocessor bo\"\n3. Save the file\n4. Restart snort","sysaffected":"","thanks":"This vulnerability was researched and reported by Internet Security Systems (ISS).","author":"This document was written by Art Manion and Jeff Gennari.","public":["http://www.snort.org/pub-bin/snortnews.cgi#99","http://www.snort.org/docs/change_logs/2.4.3/Changelog.txt","http://www.snort.org/docs/snort_htmanuals/htmanual_2.4/node11.html#SECTION00310000000000000000","http://xforce.iss.net/xforce/alerts/id/207","http://secunia.com/advisories/17220/"],"cveids":["CVE-2005-3252"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2005-10-14T14:49:45Z","publicdate":"2005-10-18T00:00:00Z","datefirstpublished":"2005-10-18T14:30:46Z","dateupdated":"2005-11-11T06:14:25Z","revision":39,"vrda_d1_directreport":"0","vrda_d1_population":"2","vrda_d1_impact":"4","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"8","cam_population":"15","cam_impact":"20","cam_easeofexploitation":"12","cam_attackeraccessrequired":"20","cam_scorecurrent":"31.05","cam_scorecurrentwidelyknown":"37.8","cam_scorecurrentwidelyknownexploited":"64.8","ipprotocol":"","cvss_accessvector":"--","cvss_accesscomplexity":"--","cvss_authentication":null,"cvss_confidentialityimpact":"--","cvss_integrityimpact":"--","cvss_availabilityimpact":"--","cvss_exploitablity":null,"cvss_remediationlevel":"Not Defined (ND)","cvss_reportconfidence":"Not Defined (ND)","cvss_collateraldamagepotential":"Not Defined (ND)","cvss_targetdistribution":"Not Defined (ND)","cvss_securityrequirementscr":"Not Defined (ND)","cvss_securityrequirementsir":"Not Defined (ND)","cvss_securityrequirementsar":"Not Defined (ND)","cvss_basescore":"0","cvss_basevector":"AV:--/AC:--/Au:--/C:--/I:--/A:--","cvss_temporalscore":"0","cvss_environmentalscore":"0","cvss_environmentalvector":"CDP:Not Defined (ND)/TD:Not Defined (ND)/CR:Not Defined (ND)/IR:Not Defined (ND)/AR:Not Defined (ND)","metric":31.05,"vulnote":null}