Microsoft Internet Explorer 11 on Win10 injection

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.
5.2$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Microsoft Internet Explorer 11 on Win10. The impacted element is an unknown function. The manipulation leads to injection. This vulnerability is listed as CVE-2017-0154. The attack may be initiated remotely. There is no available exploit. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Microsoft Internet Explorer 11 on Win10 (Web Browser). It has been rated as critical. This issue affects an unknown functionality. The manipulation with an unknown input leads to a injection vulnerability. Using CWE to declare the problem leads to CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability.

The bug was discovered 03/14/2017. The weakness was presented 03/14/2017 with Microsoft as MS17-006 as confirmed bulletin (Technet). The advisory is shared at technet.microsoft.com. The identification of this vulnerability is CVE-2017-0154 since 09/09/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 12/25/2024). It is expected to see the exploit prices for this product decreasing in the near future.MITRE ATT&CK project uses the attack technique T1055 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 97729 (MS17-006: Cumulative Security Update for Internet Explorer (4013073)), 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 91333 (Microsoft Cumulative Security Update for Internet Explorer (MS17-006)).

Applying the patch MS17-006 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 Tenable (97729), SecurityFocus (BID 96766†) and SecurityTracker (ID 1038008†). See VDB-97301, VDB-97962, VDB-97963 and VDB-97964 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Support

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.2

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

NVD Base Score: 4.4
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Injection
CWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 97729
Nessus Name: MS17-006: Cumulative Security Update for Internet Explorer (4013073)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 802074
OpenVAS Name: Microsoft Internet Explorer Multiple Vulnerabilities (4013073)
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: MS17-006

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/14/2017 +0 days 🔍
03/15/2017 +1 days 🔍
03/16/2017 +1 days 🔍
12/25/2024 +2841 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: MS17-006
Organization: Microsoft
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-0154 (🔍)
GCVE (CVE): GCVE-0-2017-0154
GCVE (VulDB): GCVE-100-97973

OVAL: 🔍

SecurityFocus: 96766 - Microsoft Internet Explorer CVE-2017-0154 Remote Privilege Escalation Vulnerability
OSVDB: - CVE-2017-0154 - MS17-006 - Microsoft - Internet Explorer - Privilege Escalation Issue
SecurityTracker: 1038008

See also: 🔍

Entryinfo

Created: 03/15/2017 10:58
Updated: 12/25/2024 10:11
Changes: 03/15/2017 10:58 (85), 09/07/2020 09:06 (2), 12/25/2024 10:11 (17)
Complete: 🔍
Cache ID: 216:F51: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!