Vulmon
Recent Vulnerabilities
Product List
Research Posts
Trends
Blog
About
Contact
Vulmon Alerts
By Relevance
By Risk Score
By Publish Date
microsoft publisher vulnerabilities and exploits
(subscribe to this query)
1000
VMScore
CVE-2003-0347
Heap-based buffer overflow in VBE.DLL and VBE6.DLL of Microsoft Visual Basic for Applications (VBA) SDK 5.0 up to and including 6.3 allows remote malicious users to execute arbitrary code via a document with a long ID parameter.
Microsoft Visual Basic 6.3
Microsoft Visual Basic 5.0
Microsoft Project 2000
Microsoft Office 2000
Microsoft Visio 2002
Microsoft Project 2002
Microsoft Office Xp
Microsoft Visual Basic 6.2
1 EDB exploit
960
VMScore
CVE-2004-0200
Buffer overflow in the JPEG (JPG) parsing engine in the Microsoft Graphic Device Interface Plus (GDI+) component, GDIPlus.dll, allows remote malicious users to execute arbitrary code via a JPEG image with a small JPEG COM field length that is normalized to a large integer length ...
Microsoft Frontpage 2003
Microsoft Visual J# .net 2003
Microsoft Visual C++ 2003
Microsoft Digital Image Pro 9
Microsoft Visual Studio .net 2003
Microsoft Project 2002
Microsoft Visual Basic 2003
Microsoft Visual C++ 2002
Microsoft Project 2003
Microsoft Picture It 7.0
Microsoft Powerpoint 2002
Microsoft Office Xp
Microsoft Outlook 2003
Microsoft Digital Image Suite 9
Microsoft Powerpoint 2003
Microsoft Infopath 2003
Microsoft Publisher 2002
Microsoft Visual Basic 2002
Microsoft Frontpage 2002
Microsoft Word 2003
Microsoft Excel 2002
Microsoft Picture It 2002
6 EDB exploits
890
VMScore
CVE-2013-1319
Microsoft Publisher 2003 SP3 does not properly check the return value of an unspecified method, which allows remote malicious users to execute arbitrary code via a crafted Publisher file, aka "Publisher Return Value Handling Vulnerability."
Microsoft Publisher 2003
890
VMScore
CVE-2013-1320
Buffer overflow in Microsoft Publisher 2003 SP3 allows remote malicious users to execute arbitrary code via a crafted Publisher file, aka "Publisher Buffer Overflow Vulnerability."
Microsoft Publisher 2003
890
VMScore
CVE-2013-1318
Microsoft Publisher 2003 SP3 allows remote malicious users to execute arbitrary code via a crafted Publisher file that triggers access to an invalid pointer, aka "Publisher Corrupt Interface Pointer Vulnerability."
Microsoft Publisher 2003
890
VMScore
CVE-2013-1322
Microsoft Publisher 2003 SP3 does not properly check table range data, which allows remote malicious users to execute arbitrary code via a crafted Publisher file, aka "Publisher Invalid Range Check Vulnerability."
Microsoft Publisher 2003
890
VMScore
CVE-2008-0102
Unspecified vulnerability in Microsoft Office Publisher 2000, 2002, and 2003 SP2 allows remote malicious users to execute arbitrary code via a crafted .pub file, related to invalid "memory values," aka "Publisher Invalid Memory Reference Vulnerability."
Microsoft Publisher 2000
Microsoft Publisher 2002
Microsoft Publisher 2003
890
VMScore
CVE-2007-1117
Unspecified vulnerability in Publisher 2007 in Microsoft Office 2007 allows remote malicious users to execute arbitrary code via unspecified vectors, related to a "file format vulnerability." NOTE: this information is based upon a vague pre-advisory with no actionable i...
Microsoft Publisher 2007
828
VMScore
CVE-2017-8725
A remote code execution vulnerability exists in Microsoft Publisher 2007 Service Pack 3 and Microsoft Publisher 2010 Service Pack 2 when they fail to properly handle objects in memory, aka "Microsoft Office Publisher Remote Code Execution".
Microsoft Publisher 2010
Microsoft Publisher 2007
828
VMScore
CVE-2016-7289
Microsoft Publisher 2010 SP2 allows remote malicious users to execute arbitrary code or cause a denial of service (memory corruption) via a crafted document, aka "Microsoft Office Memory Corruption Vulnerability."
Microsoft Publisher 2010
VMScore
CVSSv2
CVSSv3
VMScore
Recommendations:
CVE-2024-37316
firmware
CVE-2024-30078
CVE-2024-5995
remote code execution
logic flaw
CVE-2024-20693
CVE-2024-37315
CVE-2024-5464
Vulnerability Notification Service
You don’t have to wait for vulnerability scanning results
Get Started
1
2
3
4
5
NEXT »