Apply updates per vendor instructions.
Evidence dossier
CVE-2013-1331
CVE-2013-1331
gen-56ccdaf9Normalized restatement
Buffer overflow in Microsoft Office 2003 SP3 and Office 2011 for Mac allows remote attackers to execute arbitrary code via crafted PNG data in an Office document, leading to improper memory allocation, aka "Office Buffer Overflow Vulnerability."
- State
- PUBLISHED
- Published
- Jun 12, 2013
- Updated
- Oct 22, 2025
- Evidence coverage
- 72%
2026-07-18 · v2026.06.15 · percentile 99.6%
Distinct CVSS assessments remain side by side; none are averaged.
Source comparison
Who said what
Buffer overflow in Microsoft Office 2003 SP3 and Office 2011 for Mac allows remote attackers to execute arbitrary code via crafted PNG data in an Office document, leading to improper memory allocation, aka "Office Buffer Overflow Vulnerability."
Microsoft Office Buffer Overflow Vulnerability
Probability 0.818770000000; percentile 0.996120000000
Applicability
Cited product scope
[{"status": "affected", "version": "n/a"}]unknowncpe:2.3:a:microsoft:office:2003:sp3:*:*:*:*:*:*supportedcpe:2.3:a:microsoft:office:2011:*:*:*:*:macos:*:*supportedAssessments
CVSS by origin
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAV:N/AC:M/Au:N/C:C/I:C/A:CCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HLimitations and unknowns
- KEV membership is authoritative for the catalog, not proof of exposure in any environment.
- EPSS is a dated model probability and not an individual-environment prediction.
- Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
- NVD-carried upstream facts remain derivative and are not independent corroboration.
- Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
- NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
- Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
- Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.