On Sun, Mar 12, 2023 at 9:44 AM Meir Shpilraien <[email protected]> wrote:
>
> Hello v8-dev,
>
> I saw some CVE descriptions which look like this:
>
> Type confusion in V8 in Google Chrome prior to 111.0.5563.64 allowed a remote 
> attacker to potentially exploit heap corruption via a crafted HTML page. 
> (Chromium security severity: High)
>
> I tried to find more specific information about such CVE's but seems like 
> such information is not public. I want to know if a pure V8 is expose to such 
> CVE's or is it only in the integration with chromium?
>
> I am asking because I want to estimate how much I am expose to such CVE's 
> assuming my application only embeds V8.
>
> I took the CVE list from here:
> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=v8
>
> Thanks,
> Meir

Type confusion is (to the best of my knowledge) always a bug in V8. If
you are executing untrusted JS code, then your application is likely
affected.

The CVE you used an example is CVE-2023-1214 and was a bug in V8's
serializer. If you don't use that, you're _probably_ not affected -
but why take chances?

-- 
-- 
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- 
You received this message because you are subscribed to the Google Groups 
"v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-dev/CAHQurc9Y08iNLGDzKD8L1NxYhJXjnFHZ4T6GaBwLCxT_7Q3U9A%40mail.gmail.com.

Reply via email to