Antivirus and Security Software from Sophos

Psst, Mac user! We have a free Mac anti-virus just for you.

Online support

Product maintenance

Contact support

Support services

Resource centers

UK IT Security Events

Get the low-down on our cup winning security solutions to provide you with a defence dream team

MS10-045 - Vulnerability in Microsoft Office Outlook Could Allow Remote Code Execution (978212)

Back to Latest vulnerabilities homepage

Click any highlighted term for further explanation.

Details
Vulnerability name/brief description

MS10-045 - Vulnerability in Microsoft Office Outlook Could Allow Remote Code Execution (978212)

CVE/CAN name CVE-2010-0266
Vendor threat level Important
SophosLabs threat level Medium
Solution

MS10-045

Vendor description This security update resolves a privately reported vulnerability that could allow remote code execution if a user opened an attachment in a specially crafted e-mail message using an affected version of Microsoft Office Outlook. An attacker who successfully exploited this vulnerability could gain the same rights as the local user. Users whose accounts are configured to have fewer rights on the system could be less impacted than users who operate with administrative user rights.
SophosLabs comments This update encompasses the way Microsoft Office Outlook verifies attachments in a specially crafted e-mail message. The fact that this vulnerability has not been publicly disclosed, and that we are yet to see any malware that exploit these issues have been considered when assigning the SophosLabs threat rating of Medium, although we do recommend that users apply this patch at their earliest convenience.
SophosLabs testing result N/A
Currently known exploits At the time of writing SophosLabs have not observed any malware attempting to exploit this vulnerability. Should this situation change samples will be analyzed and we will take action as necessary.
First sample seen At the time of writing SophosLabs have not observed any malware attempting to exploit this vulnerability. Should this situation change samples will be analyzed and we will take action as necessary.
Discovery date July 13, 2010
Affected software Microsoft Office XP Service Pack 3
Microsoft Office 2003 Service Pack 3
2007 Microsoft Office System Service Packs 1 and 2
References http://www.microsoft.com/technet/security/bulletin/MS10-045.mspx
http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0266
Credits Microsoft MAPP
Revisions July 13, 2010 - Initial analysis written

Explanation of terms

Vulnerability Name/Brief Description:
Vendor identifier plus a brief description of the type of attack.

CVE/CAN Name:
Currently assigned CVE name. If a CVE name doesn't exist the CAN name will be used until a CVE has been assigned.

Vendor Threat Level:

Threat level assigned by the vendor

SophosLabs Threat Level:
Threat level assigned by SophosLabs

  • LOW RISK - There is little chance of this vulnerability being actively exploited by malware.
  • MEDIUM RISK - There is a possibility of this vulnerability being actively exploited by malware.
  • HIGH RISK - There is a strong possibility of this vulnerability being actively exploited by malware.
  • CRITICAL RISK - This vulnerability will almost certainly be actively exploited by malware.

Solution:
Vendor-supplied Patch identifier and recommended solution, or workaround if applicable.

Vendor Description:
Summary of the cause and potential effect of the vulnerability provided by the vendor.

SophosLabs Comments:
SophosLabs' opinions and observations of the vulnerability in question.

SophosLabs Testing Result:
Details of completed lab testing, if applicable. Please note that the lab test environment may differ significantly from user environments.

Currently Known Exploits:
List of identities for known exploits, if applicable.

First Sample Seen:
Date of the first sample seen by SophosLabs.

Discovery Date:
Date of the earliest known publically disclosed advisory.

Affected Software:
Vulnerable platforms and software versions.

If you need more information or guidance, then please contact technical support.