CVE-2013-1327
First published: Wed May 15 2013(Updated: )
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."
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft Publisher | =2003-sp3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2013-1327?
CVE-2013-1327 is considered critical, as it allows remote attackers to execute arbitrary code.
How do I fix CVE-2013-1327?
To fix CVE-2013-1327, users should apply the latest security updates for Microsoft Publisher.
What versions of Microsoft Publisher are affected by CVE-2013-1327?
CVE-2013-1327 affects Microsoft Publisher 2003 SP3.
What vulnerabilities are associated with the improper memory allocation in CVE-2013-1327?
CVE-2013-1327 relates to an integer signedness error that can lead to arbitrary code execution.
Can CVE-2013-1327 be exploited remotely?
Yes, CVE-2013-1327 can be exploited by remote attackers through crafted Publisher files.
- collector/nvd-index
- agent/references
- agent/weakness
- agent/author
- agent/severity
- agent/tags
- agent/type
- agent/description
- agent/event
- agent/first-publish-date
- agent/last-modified-date
- vendor/microsoft
- canonical/microsoft publisher
- version/microsoft publisher/2003-sp3