Request: Add case study for Chrome V8 Type Confusion (CVE-2022-3723)

[Yagnapriyakatragunta]

I would like to request adding a new case study covering the Chrome V8 Type Confusion vulnerability identified as CVE-2022-3723.

This vulnerability was reported by threat researchers at Avast and was actively exploited in the wild before it was patched by Google. It involves incorrect type inference inside the V8 JavaScript engine, leading to a type confusion condition that can result in arbitrary code execution inside Chrome.

I plan to write a MITRE-style case study for this vulnerability following the official STYLE_GUIDE.md. The case study will include background, software context, the underlying weakness (CWE-843 / CWE-704), vulnerability details, exploit explanation, fix analysis, and systemic prevention recommendations.

Please let me know if anyone else is already working on this, or if you have any concerns before I proceed.

[abuttner]

A proposed case study was submitted, but at the time Google had not made the vulnerable and fixed code public. We are keeping this issue open for now. If the code can be found, please update the case study to walk the reader through the actual code and submit a new pull request.