published 15 May 2013 · updated 6 Aug 2024
Integer signedness error in Microsoft Publisher 2003 SP3 allows remote attackers to execute arbitrary code via a crafted Publisher file…
5.5MediumEPSS 21%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 21%. No fixed version is recorded.
Integer signedness error in Microsoft Publisher 2003 SP3 allows remote attackers to execute arbitrary code via a crafted Publisher file that triggers an improper memory allocation, aka "Publisher Signed Integer Vulnerability."
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket