CVE-2006-1540: Code Injection
MSO.DLL in Microsoft Office 2000, Office XP (2002), and Office 2003 allows user-assisted attackers to cause a denial of service and execute arbitrary code via multiple attack vectors, as originally demonstrated using a crafted document record with a malformed string, as demonstrated by replacing a certain "01 00 00 00" byte sequence with an "FF FF FF FF" byte sequence, possibly causing an invalid array index, in (1) an Excel .xls document, which triggers an access violation in ole32.dll; (2) an Excel .xlw document, which triggers an access violation in excel.exe; (3) a Word document, which triggers an access violation in mso.dll in winword.exe; and (4) a PowerPoint document, which triggers an access violation in powerpnt.txt. NOTE: after the initial disclosure, this issue was demonstrated by triggering an integer overflow using an inconsistent size for a Unicode "Sheet Name" string.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2006-1540?
CVE-2006-1540 has been classified as a potential security vulnerability that can lead to denial of service and arbitrary code execution.
How do I fix CVE-2006-1540?
To mitigate CVE-2006-1540, it is recommended to apply the latest security updates released by Microsoft for affected versions of Microsoft Office.
Which versions of Microsoft Office are affected by CVE-2006-1540?
CVE-2006-1540 affects Microsoft Office 2000, Office XP (2002), and Office 2003.
What types of attacks can exploit CVE-2006-1540?
CVE-2006-1540 can be exploited through crafted document records that contain malformed strings.
Is user interaction required to exploit CVE-2006-1540?
Yes, CVE-2006-1540 typically requires user interaction, such as opening a maliciously crafted document.