Microsoft Office 2007/2010/2011 Word Document Parser resource management

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.0$0-$5k0.00

Summaryinfo

A vulnerability was found in Microsoft Office 2007/2010/2011. It has been rated as critical. Affected by this issue is some unknown functionality of the component Word Document Parser. The manipulation leads to resource management. This vulnerability is referenced as CVE-2011-1983. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Microsoft Office 2007/2010/2011 (Office Suite Software). It has been rated as critical. This issue affects an unknown function of the component Word Document Parser. The manipulation with an unknown input leads to a resource management vulnerability. Using CWE to declare the problem leads to CWE-399. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Use-after-free vulnerability in Microsoft Office 2007 SP2 and SP3, Office 2010 Gold and SP1, and Office for Mac 2011 allows remote attackers to execute arbitrary code via a crafted Word document, aka "Word Use After Free Vulnerability."

The issue has been introduced in 01/30/2007. The weakness was published 12/13/2011 by Nikita Tarakanov Alexey Sintsov (DiGiT) with ZDI as MS11-089 as confirmed bulletin (Technet). The advisory is shared at technet.microsoft.com. The identification of this vulnerability is CVE-2011-1983 since 05/09/2011. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 1778 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 57275 (MS11-089: Vulnerability in Microsoft Office Could Allow Remote Code Execution (2590602)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows : Microsoft Bulletins and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 110168 (Microsoft Office Remote Code Execution Vulnerability (MS11-089)).

Upgrading eliminates this vulnerability. Applying the patch MS11-089 is able to eliminate this problem. The bugfix is ready for download at technet.microsoft.com. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (57275), SecurityFocus (BID 50956†), Secunia (SA47098†) and SecurityTracker (ID 1026409†). Similar entry is available at VDB-4482. 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

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Resource management
CWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 57275
Nessus Name: MS11-089: Vulnerability in Microsoft Office Could Allow Remote Code Execution (2590602)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 902495
OpenVAS Name: Microsoft Office Remote Code Execution Vulnerability (2590602)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Patch: MS11-089

Timelineinfo

01/30/2007 🔍
05/09/2011 +1560 days 🔍
12/13/2011 +218 days 🔍
12/13/2011 +0 days 🔍
12/13/2011 +0 days 🔍
12/13/2011 +0 days 🔍
12/13/2011 +0 days 🔍
12/13/2011 +0 days 🔍
12/13/2011 +0 days 🔍
12/19/2011 +6 days 🔍
01/12/2025 +4773 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: MS11-089
Researcher: Nikita Tarakanov Alexey Sintsov (DiGiT)
Organization: ZDI
Status: Confirmed

CVE: CVE-2011-1983 (🔍)
GCVE (CVE): GCVE-0-2011-1983
GCVE (VulDB): GCVE-100-4445

OVAL: 🔍
IAVM: 🔍

SecurityFocus: 50956 - Microsoft Word Access Violation Remote Code Execution Vulnerability
Secunia: 47098 - Microsoft Office Word Document Parsing Use-After-Free Vulnerability, Highly Critical
SecurityTracker: 1026409

See also: 🔍

Entryinfo

Created: 12/19/2011 01:00
Updated: 01/12/2025 22:56
Changes: 12/19/2011 01:00 (92), 04/28/2019 09:39 (1), 01/12/2025 22:56 (18)
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 ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!