Show filters
36 Total Results
Displaying 31-36 of 36
Sort by:
Attacker Value
Unknown
CVE-2005-0249
Disclosure Date: February 08, 2005 (last updated February 22, 2025)
Heap-based buffer overflow in the DEC2EXE module for Symantec AntiVirus Library allows remote attackers to execute arbitrary code via a UPX compressed file containing a negative virtual offset to a crafted PE header.
0
Attacker Value
Unknown
CVE-2004-0848
Disclosure Date: February 08, 2005 (last updated February 22, 2025)
Buffer overflow in Microsoft Office XP allows remote attackers to execute arbitrary code via a link with a URL file location containing long inputs after (1) "%00 (null byte) in .doc filenames or (2) "%0a" (carriage return) in .rtf filenames.
0
Attacker Value
Unknown
CVE-2004-0573
Disclosure Date: September 28, 2004 (last updated February 22, 2025)
Buffer overflow in the converter for Microsoft WordPerfect 5.x on Office 2000, Office XP, Office 2003, and Works Suites 2001 through 2004 allows remote attackers to execute arbitrary code via a malicious document or website.
0
Attacker Value
Unknown
CVE-2003-0994
Disclosure Date: February 03, 2004 (last updated February 22, 2025)
The GUI functionality for an interactive session in Symantec LiveUpdate 1.70.x through 1.90.x, as used in Norton Internet Security 2001 through 2004, SystemWorks 2001 through 2004, and AntiVirus and Norton AntiVirus Pro 2001 through 2004, AntiVirus for Handhelds v3.0, allows local users to gain SYSTEM privileges.
0
Attacker Value
Unknown
CVE-2003-0820
Disclosure Date: December 15, 2003 (last updated February 22, 2025)
Microsoft Word 97, 98(J), 2000, and 2002, and Microsoft Works Suites 2001 through 2004, do not properly check the length of the "Macro names" data value, which could allow remote attackers to execute arbitrary code via a buffer overflow attack.
0
Attacker Value
Unknown
CVE-2003-0821
Disclosure Date: December 15, 2003 (last updated February 22, 2025)
Microsoft Excel 97, 2000, and 2002 allows remote attackers to execute arbitrary code via a spreadsheet with a malicious XLM (Excel 4) macro that bypasses the macro security model.
0