<p>CVE-2015-2460<br></p><p>We have encountered a number of Windows kernel crashes in the ATMFD.DLL OpenType driver while processing corrupted OTF font files, such as:</p><p> </p><p>---</p><p>PAGE_FAULT_IN_NONPAGED_AREA (50)</p><p>Invalid system memory was referenced. This cannot be protected by try-except,</p><p>it must be protected by a Probe. Typically the address is just plain bad or it</p><p>is pointing at freed memory.</p><p>Arguments:</p><p>Arg1: fff82008, memory referenced.</p><p>Arg2: 00000000, value 0 = read operation, 1 = write operation.</p><p>Arg3: 91a3440b, If non-zero, the instruction address which referenced the bad memory</p><p> address.</p><p>Arg4: 00000000, (reserved)</p><p> </p><p>Debugging Details:</p><p>------------------</p><p> </p><p>*** ERROR: Module load completed but symbols could not be loaded for ATMFD.DLL</p><p> </p><p>READ_ADDRESS: fff82008 </p><p> </p><p>FAULTING_IP: </p><p>ATMFD+3440b</p><p>91a3440b 8b7e08 mov edi,dword ptr [esi+8]</p><p> </p><p>MM_INTERNAL_CODE: 0</p><p> </p><p>IMAGE_NAME: ATMFD.DLL</p><p> </p><p>DEBUG_FLR_IMAGE_TIMESTAMP: 54e6a55a</p><p> </p><p>MODULE_NAME: ATMFD</p><p> </p><p>FAULTING_MODULE: 91a00000 ATMFD</p><p> </p><p>DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT</p><p> </p><p>BUGCHECK_STR: 0x50</p><p> </p><p>PROCESS_NAME: csrss.exe</p><p> </p><p>CURRENT_IRQL: 2</p><p> </p><p>ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre</p><p> </p><p>TRAP_FRAME: 97ff8d54 -- (.trap 0xffffffff97ff8d54)</p><p>ErrCode = 00000000</p><p>eax=ff677018 ebx=00000001 ecx=00000001 edx=0000000b esi=fff82000 edi=fb63e940</p><p>eip=91a3440b esp=97ff8dc8 ebp=97ff8de8 iopl=0 nv up ei ng nz na pe nc</p><p>cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286</p><p>ATMFD+0x3440b:</p><p>91a3440b 8b7e08 mov edi,dword ptr [esi+8] ds:0023:fff82008=jQuery21405247601568698883_1441098789680??????</p><p>Resetting default scope</p><p> </p><p>LAST_CONTROL_TRANSFER: from 82724ce7 to 826c02d8</p><p> </p><p>STACK_TEXT: </p><p>97ff88a4 82724ce7 00000003 4b979438 00000065 nt!RtlpBreakWithStatusInstruction</p><p>97ff88f4 827257e5 00000003 00000000 00000000 nt!KiBugCheckDebugBreak+0x1c</p><p>97ff8cb8 826d3391 00000050 fff82008 00000000 nt!KeBugCheck2+0x68b</p><p>97ff8d3c 82685c48 00000000 fff82008 00000000 nt!MmAccessFault+0x104</p><p>97ff8d3c 91a3440b 00000000 fff82008 00000000 nt!KiTrap0E+0xdc</p><p>WARNING: Stack unwind information not available. Following frames may be wrong.</p><p>97ff8de8 91a345f7 fb6ba380 0000000b fb6ba3ac ATMFD+0x3440b</p><p>97ff8e10 91a29eec fb63e8c0 ff6770d8 91a463ec ATMFD+0x345f7</p><p>97ff8e34 91a2e987 fb8f4c70 91a463ec 00000f5c ATMFD+0x29eec</p><p>97ff9544 91a2f6e0 fb8f4c70 91a3f028 97ff9790 ATMFD+0x2e987</p><p>97ff9600 91a227ae fb8f4c70 91a3f028 97ff9790 ATMFD+0x2f6e0</p><p>97ff96ec 91a22858 fb8f4c70 97ff9790 97ff9814 ATMFD+0x227ae</p><p>97ff9718 91a132b2 fb8f4c70 91a3f028 97ff9790 ATMFD+0x22858</p><p>97ff987c 91a13689 ffffffff 97ff999c fb68af58 ATMFD+0x132b2</p><p>97ff98d0 91a0406d ffffffff 97ff999c 00000000 ATMFD+0x13689</p><p>97ff9924 91b2dcf2 ff7a5010 fb700cf0 00000001 ATMFD+0x406d</p><p>97ff996c 91b167cb ff7a5010 fb700cf0 00000001 win32k!PDEVOBJ::QueryFontData+0x3e</p><p>97ff99e0 91b41513 ffa6a130 fb93cb14 000000e0 win32k!xInsertMetricsRFONTOBJ+0x9c</p><p>97ff9a14 91b435f5 00000020 97ff9a3c 97ff9c74 win32k!RFONTOBJ::bGetGlyphMetrics+0x131</p><p>97ff9cb8 91b56684 020101c3 00000100 00000020 win32k!GreGetCharABCWidthsW+0x147</p><p>97ff9d14 82682a66 020101c3 000000c0 00000040 win32k!NtGdiGetCharABCWidthsW+0xf8</p><p>97ff9d14 76ee70f4 020101c3 000000c0 00000040 nt!KiSystemServicePostCall</p><p>002cf224 00000000 00000000 00000000 00000000 ntdll!KiFastSystemCallRet</p><p>---</p><p> </p><p>The crash represents a read from invalid memory; prior to being dereferenced as an address, the ESI register is loaded with a value from EAX+0x30 (on 32-bit Windows), which points into an "Adbe" pool allocation:</p><p> </p><p>---</p><p>0: kd> !pool 9d619018</p><p>Pool page 9d619018 region is Paged session pool</p><p>9d619000 is not a valid large pool allocation, checking large session pool...</p><p>*9d619000 : large page allocation, Tag is Adbe, size is 0x4018 bytes</p><p> Pooltag Adbe : Adobe's font driver</p><p>---</p><p> </p><p>The surrounding code is a loop over a linked list of structures; the ESI register at the time of the crash holds a [F/B]link address which points to unmapped memory, potentially suggesting that the root cause of the crash is a use-after-free condition, or some kind of corruption of the linked list. Since the invalid address is later used to manipulate memory, we expect that this issue could be used to achieve remote code execution in the security context of the Windows kernel.</p><p> </p><p>Moreover, we have also encountered similar crashes one instruction further in the code - in these cases, ESI turned out to accidentally point to mapped memory, but its contents did not correspond to the ATMFD's expectations (reinforcing the use-after-free hypothesis), thus resulting in an attempt to dereference a completely wild memory address, e.g.:</p><p> </p><p>---</p><p>PAGE_FAULT_IN_NONPAGED_AREA (50)</p><p>Invalid system memory was referenced. This cannot be protected by try-except,</p><p>it must be protected by a Probe. Typically the address is just plain bad or it</p><p>is pointing at freed memory.</p><p>Arguments:</p><p>Arg1: eebd8451, memory referenced.</p><p>Arg2: 00000000, value 0 = read operation, 1 = write operation.</p><p>Arg3: 9205440e, If non-zero, the instruction address which referenced the bad memory</p><p> address.</p><p>Arg4: 00000002, (reserved)</p><p>---</p><p> </p><p>The issue reproduces on Windows 7 and 8.1. It is easiest to reproduce with Special Pools enabled for ATMFD.DLL (leading to an immediate crash when the bug is triggered), but it should also be possible to observe a crash on a default Windows installation in ATMFD.DLL.</p><p> </p><p>Note that this crash is very similar in its nature to Issue 383 (invalid memory access while traversing a linked list of "Adbe" structures); however, due to uncertainty about the reason of the crash and the different stack traces, I am filing this as a separate report for now.</p><p> </p><p>Attached is an archive with six proof of concept font files (three for each crash location) together with corresponding kernel crash logs.</p><p> </p>
京公网安备 11010502034610号
暂无评论