Microsoft Office up to 2013 SP1 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 has been found in Microsoft Office 2007 SP3/2010 SP2/2011/2013 RT SP1/2013 SP1 and classified as critical. This impacts an unknown function. This manipulation causes memory corruption. This vulnerability is tracked as CVE-2015-1683. No exploit exists. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in Microsoft Office 2007 SP3/2010 SP2/2011/2013 RT SP1/2013 SP1 (Office Suite Software). It has been declared as critical. Affected by this vulnerability is an unknown part. 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:

Microsoft Office 2007 SP3 allows remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Office Memory Corruption Vulnerability."

The weakness was disclosed 05/12/2015 by Jack Tang with Trend Micro as MS15-046 as confirmed bulletin (Technet). The advisory is shared at technet.microsoft.com. This vulnerability is known as CVE-2015-1683 since 02/17/2015. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 83416 (MS15-046: Vulnerabilities in Microsoft Office Could Allow Remote Code Execution (3057181)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows : Microsoft Bulletins. The commercial vulnerability scanner Qualys is able to test this issue with plugin 110255 (Microsoft Office Remote Code Execution Vulnerabilities (MS15-046)).

Applying the patch MS15-046 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 21614.

The vulnerability is also documented in the databases at Tenable (83416), SecurityFocus (BID 74484†), SecurityTracker (ID 1032295†) and Vulnerability Center (SBV-50041†). Additional details are provided at krebsonsecurity.com. The entries VDB-75247, VDB-75248, VDB-75249 and VDB-75250 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

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: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 83416
Nessus Name: MS15-046: Vulnerabilities in Microsoft Office Could Allow Remote Code Execution (3057181)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 804423
OpenVAS Name: Microsoft Office Word Remote Code Execution Vulnerability (3057181)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

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

Patch: MS15-046
TippingPoint: 🔍

McAfee IPS: 🔍
McAfee IPS Version: 🔍

Fortigate IPS: 🔍

Timelineinfo

02/17/2015 🔍
05/12/2015 +84 days 🔍
05/12/2015 +0 days 🔍
05/12/2015 +0 days 🔍
05/12/2015 +0 days 🔍
05/12/2015 +0 days 🔍
05/13/2015 +1 days 🔍
05/13/2015 +0 days 🔍
05/13/2015 +0 days 🔍
05/17/2022 +2561 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: MS15-046
Researcher: Jack Tang
Organization: Trend Micro
Status: Confirmed

CVE: CVE-2015-1683 (🔍)
GCVE (CVE): GCVE-0-2015-1683
GCVE (VulDB): GCVE-100-75337

OVAL: 🔍

SecurityFocus: 74484 - Microsoft Office CVE-2015-1683 Memory Corruption Vulnerability
SecurityTracker: 1032295 - Microsoft Office File Processing Flaws Let Remote Users Execute Arbitrary Code
Vulnerability Center: 50041 - [MS15-046] Microsoft Office 2007 Remote Code Execution via a Crafted Office File - CVE-2015-1683, Critical

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 05/13/2015 12:18
Updated: 05/17/2022 09:28
Changes: 05/13/2015 12:18 (80), 06/28/2017 06:27 (7), 05/17/2022 09:28 (3)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

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!