https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 18 Oct 2026 12:55:40 +0000 https://cve.radiocsirt.org/vuln/certa-2006-avi-286 certa-2006-avi-286 https://cve.radiocsirt.org/vuln/certa-2006-avi-286 https://cve.radiocsirt.org/vuln/euvd-2026-139894 EUVD-2026-139894 https://cve.radiocsirt.org/vuln/euvd-2026-139894 https://cve.radiocsirt.org/vuln/fkie_cve-2006-1540 <p>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 &#34;01 00 00 00&#34; byte sequence with an &#34;FF FF FF FF&#34; 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 &#34;Sheet Name&#34; string.</p> <p>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 &#34;01 00 00 00&#34; byte sequence with an &#34;FF FF FF FF&#34; 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 &#34;Sheet Name&#34; string.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2006-1540 https://cve.radiocsirt.org/vuln/ghsa-94cj-9f3f-7q8j <p>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 &#34;01 00 00 00&#34; byte sequence with an &#34;FF FF FF FF&#34; 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 &#34;Sheet Name&#34; string.</p> <p>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 &#34;01 00 00 00&#34; byte sequence with an &#34;FF FF FF FF&#34; 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 &#34;Sheet Name&#34; string.</p> https://cve.radiocsirt.org/vuln/ghsa-94cj-9f3f-7q8j https://cve.radiocsirt.org/vuln/gsd-2006-1540 gsd-2006-1540 https://cve.radiocsirt.org/vuln/gsd-2006-1540