{"vuid":"VU#520718","idnumber":"520718","name":"BlackBerry Enterprise Server fails to properly handle Microsoft Word attachments","keywords":["BlackBerry Enterprise Server","BlackBerry Attachment Service","arbitrary code execution","Microsoft Word file",".doc","BES"],"overview":"A buffer overflow vulnerability in BlackBerry Enterprise Server may allow a remote attacker to execute arbitrary code.","clean_desc":"A buffer overflow vulnerability exists in the BlackBerry Attachment Service component of BlackBerry Enterprise Server. This vulnerability may allow a remote attacker to execute arbitrary code when the service fails to handle a malformed Microsoft Word (.doc) document. BlackBerry states that the following systems are vulnerable: BlackBerry Enterprise Server 2.2 and later for IBM Lotus Domino\nBlackBerry Enterprise Server 3.6 and later for Microsoft Exchange\nBlackBerry Enterprise Server 4.0 and later for Novell GroupWise","impact":"A remote attacker who can successfully convince a user to open a malicious Microsoft Word attachment on a BlackBerry Handheld device may be able to execute arbitrary code and compromise a vulnerable server.","resolution":"BlackBerry provides the following solutions: Microsoft Exchange\nFor BlackBerry Enterprise Server 3.6, Install Service Pack 7. For BlackBerry Enterprise Server 4.0, Install Service Pack 3, then install version 4.0 Service Pack 3 Hotfix 3. IBM Lotus Domino\nFor BlackBerry Enterprise Server 2.2, a resolution for this issue has been developed and is currently undergoing testing. A software upgrade will be made available as soon as testing is complete. For BlackBerry Enterprise Server 4.0, install Service Pack 3, then install version 4.0 Service Pack 3 Hotfix 4. Novell GroupWise\nInstall BlackBerry Enterprise Server 4.0 Service Pack 3, then install version 4.0 Service Pack 3 Hotfix 1.","workarounds":"Workarounds BlackBerry provides the following workaround: BlackBerry Enterprise Server administrators can exclude Microsoft Word (.doc) files from being processed by the Attachment Service in the BlackBerry Enterprise Server, or disable the Attachment Service completely. To Exclude Microsoft Word (.doc) files from being processed by the Attachment Service: On the desktop, click Start > Programs > BlackBerry Enterprise Server > BlackBerry Enterprise Server Configuration. In the Format Extensions field, delete the .doc extension. Note: Format Extensions is an editable field that lists all the extensions that the Attachment Service will open. A colon is used as a delimiter. Click Apply, then click OK. Even though the .doc extension has been removed from the list of supported file types, the Attachment Service may automatically detect a .doc file with a renamed extension and attempt to process the file. Administrators may need to disable the Attachment Service. To disable the Attachment Service\nIn Microsoft Windows® Administrative Tools, double-click Services. Right-click BlackBerry Attachment Service, then click Stop. Close the Services window.","sysaffected":"","thanks":"This vulnerability was reported by \nBlackBerry","author":"This document was written by Katie Washok.","public":["http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/8021/8149/8052/Support_-_Corrupt_Word_file_may_cause_buffer_overflow_in_the_BlackBerry_Attachment_Service.html?nodeid=1181753&vernum=2","http://www.frsirt.com/english/advisories/2006/0530"],"cveids":["CVE-2006-0761"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2006-02-14T17:37:04Z","publicdate":"2006-02-09T00:00:00Z","datefirstpublished":"2006-08-21T13:17:44Z","dateupdated":"2006-08-21T17:46:33Z","revision":14,"vrda_d1_directreport":"0","vrda_d1_population":"4","vrda_d1_impact":"3","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"0","cam_population":"8","cam_impact":"10","cam_easeofexploitation":"2","cam_attackeraccessrequired":"13","cam_scorecurrent":"0.585","cam_scorecurrentwidelyknown":"0.78","cam_scorecurrentwidelyknownexploited":"1.56","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":0.585,"vulnote":null}