Microsoft Silverlight 5 Graphics 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.
6.7$0-$5k0.00

Summaryinfo

A vulnerability was found in Microsoft Silverlight 5. It has been rated as critical. Affected by this issue is some unknown functionality of the component Graphics Component. This manipulation causes memory corruption. This vulnerability is tracked as CVE-2017-0108. The attack is possible to be carried out remotely. Moreover, an exploit is present. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability has been found in Microsoft Silverlight 5 (Multimedia Player Software) and classified as critical. Affected by this vulnerability is an unknown function of the component Graphics Component. 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 bug was discovered 03/14/2017. The weakness was disclosed 03/14/2017 by Mateusz Jurczyk with Google Project Zero as MS17-013 as confirmed bulletin (Technet). The advisory is shared at technet.microsoft.com. This vulnerability is known as CVE-2017-0108 since 09/09/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 97794 (MS17-013: Security Update for Microsoft Graphics Component (4013075)), 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 91331 (Microsoft Windows Graphics Component Multiple Vulnerabilities (MS17-013)).

Applying the patch MS17-013 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.

The vulnerability is also documented in the databases at Exploit-DB (41647), Tenable (97794), SecurityFocus (BID 96722†) and SecurityTracker (ID 1038002†). The entries VDB-97039, VDB-98059, VDB-98060 and VDB-98061 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.0
VulDB Meta Temp Score: 6.7

VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

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: Partially
Local: Yes
Remote: Yes

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

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 97794
Nessus Name: MS17-013: Security Update for Microsoft Graphics Component (4013075)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 802074
OpenVAS Name: Microsoft Graphics Component Multiple Vulnerabilities (4013075)
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: MS17-013

Timelineinfo

09/09/2016 🔍
03/14/2017 +186 days 🔍
03/14/2017 +0 days 🔍
03/14/2017 +0 days 🔍
03/14/2017 +0 days 🔍
03/15/2017 +1 days 🔍
03/16/2017 +1 days 🔍
03/17/2017 +1 days 🔍
12/25/2024 +2840 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: MS17-013
Researcher: Mateusz Jurczyk
Organization: Google Project Zero
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-0108 (🔍)
GCVE (CVE): GCVE-0-2017-0108
GCVE (VulDB): GCVE-100-98077

OVAL: 🔍

SecurityFocus: 96722 - Microsoft Windows Graphics Component CVE-2017-0108 Remote Code Execution Vulnerability
OSVDB: - CVE-2017-0108 - MS17-013 - Microsoft - Windows - Code Execution Issue
SecurityTracker: 1038002

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

Entryinfo

Created: 03/15/2017 13:05
Updated: 12/25/2024 02:17
Changes: 03/15/2017 13:05 (69), 08/19/2020 12:28 (22), 12/25/2024 02:17 (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 know what is going to be exploited?

We predict KEV entries!