Vulnerability Note VU#927889
Microsoft OLE buffer overflow
A vulnerability in a way that various programs handle OLE objects could allow a remote attacker to execute arbitrary code on a vulnerable system.
Microsoft OLE is a technology that allows applications to create and edit compound documents. Compound documents are those consisting of one format, that contain embeddings of (or links to) documents of another format. A buffer overflow error occurs during the process that OLE uses to validate data. This error results in a vulnerability that could allow a remote attacker with the ability to supply a malicious OLE object to execute code of their choosing on a vulnerable system. Any application that uses the Windows OLE component could also be vulnerable to this issue and the attack vectors may vary between systems. Microsoft states that on Exchange Server 5.0, Exchange Server 5.5, Exchange 2000 Server, and Exchange Server 2003, any unauthenticated user who could deliver a specially crafted message to the affected system could try to exploit this vulnerability.
Furthermore, Microsoft states that on Windows 2000, Windows XP, and Windows Server 2003, user interaction is required to exploit this vulnerability. An attacker would need to persuade a user to open a file or an email message containing an attachment that contains a malicious OLE object.
A remote attacker could execute arbitrary code on a vulnerable system. The attacker-supplied code would be executed with the privileges of the component that exposes the vulnerability.
Apply a patch
Systems Affected (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|Microsoft Corporation||Affected||-||08 Feb 2005|
CVSS Metrics (Learn More)
Thanks to Microsoft Security for reporting this vulnerability.
This document was written by Chad R Dougherty based upon information provided by Microsoft.
- CVE IDs: CAN-2005-0044
- Date Public: 08 Feb 2005
- Date First Published: 08 Feb 2005
- Date Last Updated: 08 Feb 2005
- Severity Metric: 20.66
- Document Revision: 2
If you have feedback, comments, or additional information about this vulnerability, please send us email.