Lucene search

K
symantecSymantec Security ResponseSMNTC-49513
HistorySep 13, 2011 - 12:00 a.m.

Microsoft Office 'MSO.dll' Uninitialized Pointer (CVE-2011-1982) Remote Code Execution Vulnerability

2011-09-1300:00:00
Symantec Security Response
www.symantec.com
12

0.516 Medium

EPSS

Percentile

97.2%

Description

Microsoft Office is prone to a remote code-execution vulnerability. Attackers can exploit this issue by enticing an unsuspecting user to open a specially crafted Word file. Successful exploits can allow attackers to execute arbitrary code with the privileges of the user running the application. Failed exploit attempts will result in a denial-of-service condition.

Technologies Affected

  • Microsoft Office 2007
  • Microsoft Office 2007 SP1
  • Microsoft Office 2007 SP2
  • Microsoft Office 2010 (32-bit edition)
  • Microsoft Office 2010 (32-bit edition) SP1
  • Microsoft Office 2010 (64-bit edition)
  • Microsoft Office 2010 (64-bit edition) SP1
  • Microsoft Office 2010

Recommendations

Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, always run nonadministrative software as an unprivileged user with minimal access rights.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of suspicious or anomalous activity. This may help detect malicious actions that an attacker may take after successfully exploiting vulnerabilities in applications. Review all applicable logs regularly.

Do not accept or execute files from untrusted or unknown sources.
To reduce the likelihood of successful exploits, never handle files that originate from unfamiliar or untrusted sources.

Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to sites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.

Implement multiple redundant layers of security.
Since this issue may be leveraged to execute code, we recommend memory-protection schemes, such as nonexecutable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploits of memory-corruption vulnerabilities.

Vendor updates are available. Please see the references for details.