<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ie on iamelli0t's blog</title><link>https://iamelli0t.github.io/tags/ie/</link><description>Recent content in Ie on iamelli0t's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 10 Apr 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://iamelli0t.github.io/tags/ie/index.xml" rel="self" type="application/rss+xml"/><item><title>Exploiting Windows RPC to bypass CFG mitigation: analysis of CVE-2021-26411 in-the-wild sample</title><link>https://iamelli0t.github.io/2021/04/10/RPC-Bypass-CFG/</link><pubDate>Sat, 10 Apr 2021 00:00:00 +0000</pubDate><guid>https://iamelli0t.github.io/2021/04/10/RPC-Bypass-CFG/</guid><description>&lt;p&gt;The general method of browser render process exploit is: after exploiting the vulnerability to obtain user mode arbitrary memory read/write primitive, the vtable of DOM/js object is tampered to hijack the code execution flow. Then VirtualProtect is called by ROP chain to modify the shellcode memory to PAGE_EXECUTE_READWRITE, and the code execution flow is jumped to shellcode by ROP chain finally. After Windows 8.1, Microsoft introduced CFG (Control Flow Guard)[1] mitigation to verify the indirect function call, which mitigates the exploitation of tampering with vtable to get code execution.&lt;br&gt;&lt;/p&gt;</description></item><item><title>CVE-2021-26411: Internet Explorer mshtml use-after-free</title><link>https://iamelli0t.github.io/2021/03/12/CVE-2021-26411/</link><pubDate>Fri, 12 Mar 2021 00:00:00 +0000</pubDate><guid>https://iamelli0t.github.io/2021/03/12/CVE-2021-26411/</guid><description>&lt;p&gt;In January of this year, Google and Microsoft respectively published blogs revealing attacks on security researchers by an APT group from NK[1][2]. A vulnerability in Internet Explorer used in this attack was fixed as CVE-2021-26411 in Microsoft&amp;rsquo;s Patch Tuesday this month[3]. The vulnerability is triggered when users of the affected version of Internet Explorer access a malicious link constructed by attackers, causing remote code execution.&lt;/p&gt;
&lt;h2 id="root-cause-analysis"&gt;Root cause analysis&lt;/h2&gt;
&lt;p&gt;The POC which can trigger the vulnerability is shown below:&lt;/p&gt;</description></item></channel></rss>