{"vuid":"VU#489397","idnumber":"489397","name":"Microsoft Server Message Block vulnerable to buffer overflow","keywords":["Microsoft","Server Message Block","SMB","buffer overflow","remote code execution","MS05-027"],"overview":"Microsoft Server Message Block (SMB) is vulnerable to a buffer handling flaw  when processing incoming SMB packets that may lead to remote code execution.","clean_desc":"Server Message Block is a protocol which allows sharing of files, printers, serial ports, and other abstractions. The SMB protocol is supported on many platforms and architectures, including many Microsoft products. The Microsoft Server Message Block implementation contains a flaw in incoming SMB packet validation that may result in a buffer receiving inappropriate data. An attacker may send a specially-crafted packet to the vulnerable host and be able to execute arbitrary code on the host after exploiting the incoming packet processing flaw.","impact":"A remote unauthenticated attacker with the ability to send specially-crafted SMB packets to a vulnerable host may be able to execute arbitrary code on that system. The attacker-supplied code would be run in the context of Local System, resulting in a complete compromise of the system.","resolution":"Apply An Update Please see Microsoft Security Bulletin MS05-027 for more information, such as workarounds and patches.","workarounds":"Utilize Workarounds Microsoft recommends the following workarounds in Microsoft Security Bulletin MS05-027: Block TCP ports 139 and 445. This will disallow attackers the ability to contact the vulnerable SMB service on the affected host(s). Use a firewall to block unsolicited or malicious traffic. Use IPsec to protect network communications between hosts.","sysaffected":"","thanks":"Thanks to Microsoft for providing information on this issue, who in turn thank \nQua\nlys for reporting the vulnerability","author":"This document was written by Ken MacInnis.","public":["http://www.microsoft.com/technet/security/bulletin/MS05-027.mspx","http://xforce.iss.net/xforce/alerts/id/195"],"cveids":["CVE-2005-1206"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2005-06-14T17:44:02Z","publicdate":"2005-06-14T00:00:00Z","datefirstpublished":"2005-06-14T21:43:49Z","dateupdated":"2005-06-14T22:36:53Z","revision":16,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"10","cam_population":"18","cam_impact":"20","cam_easeofexploitation":"14","cam_attackeraccessrequired":"14","cam_scorecurrent":"33.075","cam_scorecurrentwidelyknown":"39.69","cam_scorecurrentwidelyknownexploited":"66.15","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":33.075,"vulnote":null}