<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CVE-2021-38003 on Arzedlab 🪵</title><link>https://arzedlab.github.io/tags/cve-2021-38003/</link><description>Recent content in CVE-2021-38003 on Arzedlab 🪵</description><generator>Hugo</generator><language>en-us</language><copyright>© Ravshan</copyright><lastBuildDate>Sat, 30 Mar 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://arzedlab.github.io/tags/cve-2021-38003/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2021-38003 The Hole Leak to RCE</title><link>https://arzedlab.github.io/posts/cve-2021-38003-the-hole-leak-to-rce-ed84a7ccd2664916bb597042d3423439/</link><pubDate>Sat, 30 Mar 2024 00:00:00 +0000</pubDate><guid>https://arzedlab.github.io/posts/cve-2021-38003-the-hole-leak-to-rce-ed84a7ccd2664916bb597042d3423439/</guid><description>&lt;h1 id="cve-2021-38003--the-hole-leak-to-rce">CVE-2021-38003 | The Hole Leak to RCE&lt;/h1>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>&lt;strong>Type Of Vulnerability&lt;/strong>&lt;/th>
 &lt;th>The Hole Leak&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Security Severity&lt;/strong>&lt;/td>
 &lt;td>&lt;strong>High&lt;/strong>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Effected Components&lt;/strong>&lt;/td>
 &lt;td>&lt;strong>Javascript, Turbofan&lt;/strong>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Issue Source&lt;/strong>&lt;/td>
 &lt;td>&lt;a href="https://issues.chromium.org/issues/40057710">https://issues.chromium.org/issues/40057710&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Writeup Source(s)&lt;/strong>&lt;/td>
 &lt;td>None&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Tested Version&lt;/strong>&lt;/td>
 &lt;td>Google Chrome 95.0.4638.54 (Official Build) (x86_64)&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Vulnerable commit&lt;/strong>&lt;/td>
 &lt;td>a4252db3228433fed5c2bdb0fdff9a6b7b638f3b&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h1 id="deep-dive-into-vulnerability">Deep Dive Into Vulnerability&lt;/h1>
&lt;p>[1] The vulnerability arises as V8 attempts to handle exceptions in &lt;code>JSON.stringify()&lt;/code>. If a exception appears in the built-in function, &lt;code>pending_exception_&lt;/code> is set by the &lt;code>Isolate::set_pending_exception()&lt;/code> method. The calling code then moves to the V8 exception handling mechanism, where the &lt;code>Isolate::pending_exception()&lt;/code> member is fetched from the active isolate and the currently active JavaScript exception handler is invoked using it.&lt;/p></description></item></channel></rss>