Microsoft Office 2007 SP3, Excel 2007 SP3, PowerPoint 2007 SP3, Visio 2007 SP3, Word 2007 SP3, Office 2010 SP2, Excel 2010 SP2, PowerPoint 2010 SP2, Visio 2010 SP2, Word 2010 SP2, Office 2013 SP1, Excel 2013 SP1, PowerPoint 2013 SP1, Visio 2013 SP1, Word 2013 SP1, Excel 2013 RT SP1, PowerPoint 2013 RT SP1, Word 2013 RT SP1, Office 2016, Excel 2016, PowerPoint 2016, Visio 2016, Word 2016, and Visual Basic 6.0 Runtime allow remote attackers to bypass the ASLR protection mechanism via unspecified vectors, aka "Microsoft Office ASLR Bypass."
Why It Matters
Analysis dossierWhy It Matters
Microsoft Office 2007 SP3, Excel 2007 SP3, PowerPoint 2007 SP3, Visio 2007 SP3, Word 2007 SP3, Office 2010 SP2, Excel 2010 SP2, PowerPoint 2010 SP2, Visio 2010 SP2, Word 2010 SP2, Office 2013 SP1, Excel 2013 SP1, PowerPoint 2013 SP1, Visio 2013 SP1, Word 2013 SP1, Excel 2013 RT SP1, PowerPoint 2013 RT SP1, Word 2013 RT SP1, Office 2016, Excel 2016, PowerPoint 2016, Visio 2016, Word 2016, and Visual Basic 6.0 Runtime allow remote attackers to bypass the ASLR protection mechanism via unspecified vectors, aka "Microsoft Office ASLR Bypass."
Medium
Unknown
Unknown
Risk basis: Microsoft or Microsoft-managed product relevance; No confirmed exploitation signal in current enrichment
Affected Products & Remediation
6 source-backed products- microsoft excel · 2007; 2010; 2013; 2016 · NVD CPE · Source
- microsoft office · 2007; 2010; 2013; 2016 · NVD CPE · Source
- microsoft powerpoint · 2010; 2013; 2016 · NVD CPE · Source
- microsoft visio · 2007; 2010; 2013; 2016 · NVD CPE · Source
- microsoft visual basics · 6.0 · NVD CPE · Source
- microsoft word · 2007; 2010; 2013; 2016 · NVD CPE · Source
Vendor or catalog guidance (source)
Not provided by source
Known exploitation (source facts)
Only what a source states. Unknown means no source has said either way; it is not "not exploited".
- CISA KEV
- Unknown
- Exploited (source statement)
- Unknown
- Publicly disclosed (source)
- Unknown
Suggested hunting (rule-based inference)
SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.
Matched user-interaction-client (CVSS AV:N, CVSS UI:R)
Exposure
- Identify endpoints reporting this CVE, especially those used for email and web browsing.Telemetry: DeviceTvmSoftwareVulnerabilities · A network vector that needs user interaction points at user-facing client software. · Rule user-interaction-client
Exploitation evidence
- Review unusual child processes started by the affected client application on affected endpoints.Telemetry: DeviceProcessEvents · Hunting hypothesis from the CVSS vector; it does not show that exploitation occurred. · Rule user-interaction-client
Response
- Confirm the source-stated update on affected endpoints.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies remediation. · Rule user-interaction-client
CISA KEV Record
CISA KEV status was not determined for this record.
Change History & Source Data
— No recorded material change
- CNA / source
- secure@microsoft.com
- Record status · verification
- UPDATED · NVD API
- CPE
- cpe:2.3:a:microsoft:excel:2007:sp3:*:*:*:*:*:*, cpe:2.3:a:microsoft:excel:2010:sp2:*:*:*:*:x64:*, cpe:2.3:a:microsoft:excel:2010:sp2:*:*:*:*:x86:*, cpe:2.3:a:microsoft:excel:2013:sp1:*:*:*:*:*:*, cpe:2.3:a:microsoft:excel:2013:sp1:*:*:rt:*:*:*, cpe:2.3:a:microsoft:excel:2016:*:*:*:*:*:*:*, cpe:2.3:a:microsoft:office:2007:sp3:*:*:*:*:*:*, cpe:2.3:a:microsoft:office:2010:sp2:x64:*:*:*:*:*, cpe:2.3:a:microsoft:office:2010:sp2:x86:*:*:*:*:*, cpe:2.3:a:microsoft:office:2013:sp1:*:*:*:*:*:*
Evidence & Provenance
Linked by the query's stored exact CVE association. Review required tables and validation status before use.
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2016-0012"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel descCorrelated briefings
— No published briefing references this CVE