Microsoft Office up to XP Filename memory corruption

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, which was classified as critical, has been found in Microsoft Office up to XP. The affected element is an unknown function of the component Filename Handler. This manipulation causes memory corruption. This vulnerability is tracked as CVE-2006-3649. No exploit exists. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Microsoft Office up to XP (Office Suite Software). It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Filename Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Buffer overflow in Microsoft Visual Basic for Applications (VBA) SDK 6.0 through 6.4, as used by Microsoft Office 2000 SP3, Office XP SP3, Project 2000 SR1, Project 2002 SP1, Access 2000 Runtime SP3, Visio 2002 SP2, and Works Suite 2004 through 2006, allows user-assisted attackers to execute arbitrary code via unspecified document properties that are not verified when VBA is invoked to open documents.

The bug was discovered 08/08/2006. The weakness was disclosed 08/08/2006 by Ka Chun Leung with Symantec as MS06-047 as confirmed bulletin (Technet). The advisory is shared at microsoft.com. The public release happened without involvement of Microsoft. This vulnerability is known as CVE-2006-3649 since 07/17/2006. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

It is declared as attacked. We expect the 0-day to have been worth approximately $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 22189 (MS06-047: Vulnerability in Microsoft Visual Basic for Applications Could Allow Remote Code Execution (921645)), 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 90341 (Microsoft Visual Basic for Applications Remote Code Execution Vulnerability (MS06-047)).

Applying the patch MS06-047 is able to eliminate this problem. The bugfix is ready for download at windowsupdate.microsoft.com. A possible mitigation has been published 3 years after the disclosure of the vulnerability. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 4588.

The vulnerability is also documented in the databases at X-Force (28023), Zero-Day.cz (117), Tenable (22189), SecurityFocus (BID 19414†) and OSVDB (27849†). Additional details are provided at techworld.com. The entries VDB-2440 and VDB-2439 are pretty similar. 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: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Attacked

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 22189
Nessus Name: MS06-047: Vulnerability in Microsoft Visual Basic for Applications Could Allow Remote Code Execution (921645)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Zero-Day.cz: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

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

Patch: MS06-047
TippingPoint: 🔍

McAfee IPS: 🔍
McAfee IPS Version: 🔍

ISS Proventia IPS: 🔍
PaloAlto IPS: 🔍
Fortigate IPS: 🔍

Timelineinfo

07/17/2006 🔍
08/08/2006 +22 days 🔍
08/08/2006 +0 days 🔍
08/08/2006 +0 days 🔍
08/08/2006 +0 days 🔍
08/08/2006 +0 days 🔍
08/08/2006 +0 days 🔍
08/08/2006 +0 days 🔍
08/08/2006 +0 days 🔍
08/08/2006 +0 days 🔍
08/09/2006 +0 days 🔍
08/09/2006 +0 days 🔍
08/08/2008 +730 days 🔍
06/19/2025 +6159 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: MS06-047
Researcher: Ka Chun Leung
Organization: Symantec
Status: Confirmed

CVE: CVE-2006-3649 (🔍)
GCVE (CVE): GCVE-0-2006-3649
GCVE (VulDB): GCVE-100-2437

OVAL: 🔍

CERT: 🔍
X-Force: 28023
SecurityFocus: 19414 - Microsoft Visual Basic for Applications Document Check Buffer Overflow Vulnerability
Secunia: 21408 - Microsoft Visual Basic for Applications Buffer Overflow, Extremely Critical
OSVDB: 27849 - Microsoft Visual Basic Unspecified Document Handling Overflow
SecurityTracker: 1016656
Vulnerability Center: 12505 - [MS06-047] Microsoft Visual Basic Buffer Overflow via Unspecified Document Properties, Medium
Vupen: ADV-2006-3214

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

Entryinfo

Created: 08/09/2006 11:54
Updated: 06/19/2025 23:00
Changes: 08/09/2006 11:54 (104), 06/24/2019 09:59 (2), 07/22/2024 00:02 (24), 01/05/2025 12:21 (2), 06/19/2025 23:00 (2)
Complete: 🔍
Cache ID: 216:156: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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!