CVE-2014-6332
HIGHCVE-2014-6332 is a high-severity (CVSS 8.8) Buffer Overflow vulnerability. 26 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2014-6332 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OleAut32.dll in OLE in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and…
Exploitation Status
Actively exploited in the wild
- CISA’s SSVC triage classifies this CVE as under active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2014-6332.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2014-6332 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 368,770 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Description
OleAut32.dll in OLE in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 allows remote attackers to execute arbitrary code via a crafted web site, as demonstrated by an array-redimensioning attempt that triggers improper handling of a size value in the SafeArrayDimen function, aka "Windows OLE Automation Array Remote Code Execution Vulnerability."
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Internet Download Manager - OLE Automation Array Remote Code Execution
by Mohammad Reza Espargham · Jul 21, 2015
Microsoft Internet Explorer 11 - OLE Automation Array Remote Code Execution (1)
by yuange · Nov 13, 2014
Havij - OLE Automation Array Remote Code Execution
by Mohammad Reza Espargham · Jun 27, 2015
Microsoft Windows HTA (HTML Application) - Remote Code Execution (MS14-064)
by Mohammad Reza Espargham · Aug 17, 2015
Acunetix 9.5 - OLE Automation Array Remote Code Execution
by Naser Farhadi · Mar 27, 2015
The World Browser 3.0 Final - Remote Code Execution
by Ehsan Noreddini · Oct 22, 2015
Microsoft Internet Explorer OLE Pre-IE11 - Automation Array Remote Code Execution / PowerShell VirtualAlloc (MS14-064)
by GradiusX & b33f · Nov 20, 2014
HTML Compiler - Remote Code Execution
by Ehsan Noreddini · Oct 20, 2015
Microsoft Internet Explorer < 11 - OLE Automation Array Remote Code Execution (Metasploit)
by Wesley Neelen & Rik van Duijn · Nov 13, 2014
Detection & mitigation playbook
VulnerabilityDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for the affected component. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of the affected component has shipped for CVE-2014-6332 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2014-6332 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2014-6332. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2014-6332 in your dependencies?
O3 detects CVE-2014-6332 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.