Explore tweets tagged as #v8CTF
Another parser bug, utilized by someone in v8ctf M127
Submitted a bug but it is duplicate, move ahead. Here is the fix. Our newly developed mutators are alright . @wwkenwong.
0
3
18
This issue is due to a incomplete fix to CloneObjectIC that I mentioned in my reading notes: which is used by the first v8ctf commit. The condition function is still dog shit for now, but it works.
To those who report fuzzer crashes immediately without even looking at a single line of source code, just take a glance and your bounty will get doubled.
1
0
4
🌪️ Now at #TyphoonCon24: From Vulnerability to Victory: A Chrome Renderer 1-Day Exploit's Journey to v8CTF Glory by Haein Lee
1
7
47
Blog about issue-339736513: [v8ctf M125] v8 missing check of WasmObject type causing IC type confusion and OOB access. Shout out to @mistymntncop, i can't believe the poly IC technique from CVE-2023-3079 is still alive😅.
3
15
67