PowerPoint Viewer PowerPointViewer.ocx ActiveX control buffer overflow

office-powerpoint-ocx-bo (34013) The risk level is classified as HighHigh Risk

Description:

The Office OCX PowerPoint Viewer ActiveX control is vulnerable to a stack-based buffer overflow. By persuading a victim to visit a specially-crafted Web page that passes an overly long argument to the HttpDownloadFile() or OpenWebFile() method, a remote attacker could overflow a buffer and execute arbitrary code on the system or cause the victim's browser to crash.

Platforms Affected:

  • Office OCX, PowerPoint Viewer OCX 3.1.0.3 and prior

Remedy:

No remedy available as of July 4, 2009.

Consequences:

Gain Access

References:

  • MoAxB #01, PowerPointViewer.ocx 3.1 multiple methods DoS at http://moaxb.blogspot.com/2007/05/moaxb-01-powerpointviewerocx-31.html.
  • Office OCX Web site, PowerPoint Viewer OCX at http://www.officeocx.com/PowerPoint-Viewer-OCX.htm.
  • BID-23733: Office OCX PowerPoint Viewer ActiveX Denial of Service Vulnerabilities
  • CVE-2007-2494: Multiple stack-based buffer overflows in the PowerPointOCX ActiveX control in PowerPointViewer.ocx 3.1.0.3 allow remote attackers to cause a denial of service (Internet Explorer 7 crash) via a long (1) DoOleCommand, (2) FTPDownloadFile, (3) FTPUploadFile, (4) HttpUploadFile, (5) Save, (6) SaveWebFile, (7) HttpDownloadFile, (8) Open, or (9) OpenWebFile property value. NOTE: some of these details are obtained from third party information.
  • SA25092: PowerPoint Viewer OCX ActiveX Control Buffer Overflow Vulnerabilities
  • VUPEN/ADV-2007-1612: Office OCX PowerPoint Viewer Multiple Method Remote Code Execution Vulnerability

Reported:

May 01, 2007

The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.

For corrections or additions please email xforce@iss.net

Return to the main page