Microsoft Excel 2007 SP3/2010 SP2 Memory information disclosure

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

Summaryinfo

A vulnerability was found in Microsoft Excel 2007 SP3/2010 SP2 and classified as problematic. This affects an unknown part. The manipulation results in information disclosure (Memory). This vulnerability is cataloged as CVE-2017-0194. The attack may be launched remotely. There is no exploit available. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability classified as problematic has been found in Microsoft Excel 2007 SP3/2010 SP2 (Spreadsheet Software). Affected is an unknown code. The manipulation with an unknown input leads to a information disclosure vulnerability (Memory). CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:

Microsoft Excel 2007 SP3, Microsoft Excel 2010 SP2, and Office Compatibility Pack SP2 allow remote attackers to obtain sensitive information from process memory via a crafted Office document, aka "Microsoft Office Information Disclosure Vulnerability."

The bug was discovered 04/11/2017. The weakness was shared 04/11/2017 by Qiang Liu with McAfee (Website). The advisory is shared for download at portal.msrc.microsoft.com. This vulnerability is traded as CVE-2017-0194 since 09/09/2016. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.

The vulnerability scanner Nessus provides a plugin with the ID 99314 (Security Update for Microsoft Office Products (April 2017) (Petya)), 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 110297 (Microsoft Office and Microsoft Office Services and Web Apps Security Update April 2017).

Applying a patch is able to eliminate this problem. The bugfix is ready for download at portal.msrc.microsoft.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (99314), SecurityFocus (BID 97436†) and SecurityTracker (ID 1038244†). The entries VDB-99533, VDB-99653, VDB-99654 and VDB-99682 are related to this item. Once again VulDB remains the best source for 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: 4.9
VulDB Meta Temp Score: 4.8

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Name: Memory
Class: Information disclosure / Memory
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 99314
Nessus Name: Security Update for Microsoft Office Products (April 2017) (Petya)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 801345
OpenVAS Name: Microsoft Office Excel Information Disclosure Vulnerability (KB3191847)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

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

Patch: portal.msrc.microsoft.com

Timelineinfo

09/09/2016 🔍
04/11/2017 +214 days 🔍
04/11/2017 +0 days 🔍
04/11/2017 +0 days 🔍
04/11/2017 +0 days 🔍
04/12/2017 +1 days 🔍
04/12/2017 +0 days 🔍
04/12/2017 +0 days 🔍
04/12/2017 +0 days 🔍
11/28/2022 +2056 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: portal.msrc.microsoft.com
Researcher: Qiang Liu
Organization: McAfee
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-0194 (🔍)
GCVE (CVE): GCVE-0-2017-0194
GCVE (VulDB): GCVE-100-99684

OVAL: 🔍

SecurityFocus: 97436 - Microsoft Office CVE-2017-0194 Memory Corruption Vulnerability
OSVDB: - CVE-2017-0194 - Microsoft - Office - Information Disclosure Issue
SecurityTracker: 1038244

See also: 🔍

Entryinfo

Created: 04/12/2017 16:57
Updated: 11/28/2022 18:12
Changes: 04/12/2017 16:57 (81), 08/29/2020 16:35 (6), 11/28/2022 18:12 (4)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for 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!