Microsoft Office PICT Image Converter (CVE-2010-3946) Integer Overflow Vulnerability

2010-12-14T00:00:00
ID SMNTC-45273
Type symantec
Reporter Symantec Security Response
Modified 2010-12-14T00:00:00

Description

Description

Microsoft Office is prone to a remote integer-overflow vulnerability because the software fails to perform adequate boundary-checks on user-supplied data. An attacker can exploit this issue by enticing an unsuspecting user into opening an Office document that contains a specially crafted PICT image. Successfully exploiting this issue allows attackers to execute arbitrary code in the privilege of the currently logged in user. Failed exploit attempts will result in a denial-of-service condition.

Technologies Affected

  • Microsoft Office 2003
  • Microsoft Office 2003 SP1
  • Microsoft Office 2003 SP2
  • Microsoft Office 2003 SP3
  • Microsoft Office Converter Pack
  • Microsoft Office XP
  • Microsoft Office XP SP1
  • Microsoft Office XP SP2
  • Microsoft Office XP SP3
  • Microsoft Works 9.0

Recommendations

Run all software as a nonprivileged user with minimal access rights.
To mitigate the impact of a successful exploit, run the affected application as a 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 anomalous or suspicious activity. This includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This may indicate exploitation attempts or activity that results from successful exploitation.

Do not accept or execute files from untrusted or unknown sources.
Never accept files from untrusted or unknown sources, because they may be malicious in nature. Avoid opening email attachments from unknown or questionable sources.

Do not accept communications that originate from unknown or untrusted sources.
Do not accept or preview emails that come from unknown or unsolicited locations.

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 exploit attempts of memory-corruption vulnerabilities.

The vendor has released an advisory and updates. Please see the references for more information.