Microsoft Windows up to XP OLE Automation Array OleAut32.dll SafeArrayDimen code injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.9$0-$5k0.00

Summaryinfo

A vulnerability classified as very critical has been found in Microsoft Windows up to XP. This impacts the function SafeArrayDimen in the library OleAut32.dll of the component OLE Automation Array Handler. The manipulation leads to code injection. This vulnerability is referenced as CVE-2014-6332. Remote exploitation of the attack is possible. Furthermore, an exploit is available. This vulnerability is historically significant due to its background and the way it was received. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Microsoft Windows up to XP (Operating System). It has been rated as very critical. This issue affects the function SafeArrayDimen in the library OleAut32.dll of the component OLE Automation Array Handler. The manipulation with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability.

The issue has been introduced in 08/24/1995. The weakness was published 11/11/2014 by Robert Freeman with IBM X-Force as MS14-064 as confirmed bulletin (Technet). The advisory is shared at technet.microsoft.com. The identification of this vulnerability is CVE-2014-6332 since 09/11/2014. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/22/2026). MITRE ATT&CK project uses the attack technique T1059 for this issue. Due to its background and reception, this vulnerability has a historic impact.

A public exploit has been developed by Ehsan Noreddini in Ruby and been published 2 years after the advisory. The exploit is available at securityfocus.com. It is declared as attacked. The vulnerability was handled as a non-public zero-day exploit for at least 7019 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 79125 (MS14-064: Vulnerabilities in Windows OLE Could Allow Remote Code Execution (3011443)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows : Microsoft Bulletins. The analysis with Nessus happens with this NASL code:

if (
  # Windows 8.1 / Windows Server 2012 R2
  hotfix_is_vulnerable(os:"6.3", sp:0, file:"packager.dll", version:"6.3.9600.17408", min_version:"6.3.9600.16000", dir:"\system32", bulletin:bulletin, kb:"3010788") ||
The commercial vulnerability scanner Qualys is able to test this issue with plugin 90987 (Microsoft Windows OLE Remote Code Execution Vulnerability (MS14-064)). The CISA Known Exploited Vulnerabilities Catalog lists this issue since 03/25/2022 with a due date of 04/15/2022:
Apply updates per vendor instructions.

Applying the patch MS14-064 is able to eliminate this problem. The bugfix is ready for download at technet.microsoft.com. A possible mitigation has been published immediately after the disclosure of the vulnerability. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 16946.

The vulnerability is also documented in the databases at Exploit-DB (38500), Tenable (79125), SecurityFocus (BID 70952†), SecurityTracker (ID 1031184†) and Vulnerability Center (SBV-46987†). securityintelligence.com is providing further details. Similar entry is available at VDB-68045. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

Video

Open Video | Show More Videos

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.9

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

ADP CISA Base Score: 8.8
ADP CISA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Code injection
CWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Attacked
Author: Ehsan Noreddini
Programming Language: 🔍
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

KEV Added: 🔍
KEV Due: 🔍
KEV Remediation: 🔍
KEV Ransomware: 🔍
KEV Notice: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 79125
Nessus Name: MS14-064: Vulnerabilities in Windows OLE Could Allow Remote Code Execution (3011443)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

Saint ID: exploit_info/windows_ole_automation_array
Saint Name: Windows OLE Automation Array command execution

Qualys ID: 🔍
Qualys Name: 🔍

MetaSploit ID: ms14_064_ole_code_execution.rb
MetaSploit Name: MS14-064 Microsoft Internet Explorer Windows OLE Automation Array Remote Code Execution
MetaSploit File: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍

Patch: MS14-064
Suricata ID: 2019706
Suricata Class: 🔍
Suricata Message: 🔍

TippingPoint: 🔍

McAfee IPS: 🔍
McAfee IPS Version: 🔍

Fortigate IPS: 🔍

Timelineinfo

08/24/1995 🔍
09/11/2014 +6958 days 🔍
11/11/2014 +61 days 🔍
11/11/2014 +0 days 🔍
11/11/2014 +0 days 🔍
11/11/2014 +0 days 🔍
11/11/2014 +0 days 🔍
11/11/2014 +0 days 🔍
11/11/2014 +0 days 🔍
11/12/2014 +1 days 🔍
10/20/2015 +342 days 🔍
10/20/2015 +0 days 🔍
04/22/2026 +3837 days 🔍

Sourcesinfo

Vendor: microsoft.com
Product: microsoft.com

Advisory: MS14-064
Researcher: Robert Freeman
Organization: IBM X-Force
Status: Confirmed

CVE: CVE-2014-6332 (🔍)
GCVE (CVE): GCVE-0-2014-6332
GCVE (VulDB): GCVE-100-68165

OVAL: 🔍

CERT: 🔍
SecurityFocus: 70952 - Microsoft Windows CVE-2014-6332 OLE Remote Code Execution Vulnerability
SecurityTracker: 1031184 - Microsoft Windows OLE Automation Array Bug Lets Remote Users Execute Arbitrary Code
Vulnerability Center: 46987 - [MS14-064] Microsoft Windows Remote Code Execution in OLE - CVE-2014-6332, Critical

scip Labs: https://www.scip.ch/en/?labs.20140213
Misc.: 🔍
See also: 🔍

Entryinfo

Created: 11/12/2014 16:57
Updated: 04/22/2026 20:45
Changes: 11/12/2014 16:57 (99), 04/07/2017 15:02 (12), 02/24/2022 14:11 (3), 02/24/2022 14:13 (1), 04/24/2024 09:29 (23), 09/09/2024 22:29 (1), 12/20/2024 05:18 (1), 01/10/2025 15:20 (1), 04/22/2026 20:45 (11)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!