Explore tweets tagged as #v8CTF
@0xmadvise
no_r0llback
21 days
Old v8ctf chall but i had fun solving it while listening to tik tok and getting RCE'd inside my box
0
3
9
@buptsb
1377 High-yield Nukes
1 year
v8ctf now has bugid published.
Tweet media one
0
5
37
@xvonfers
xvonfers
2 months
If you look at v8ctf public submissions, specifically for 2025, then in almost six months only 5 have been confirmed (two of which are 0-day).And in general, there have been few serious problems in v8 so far (only one 0-day ITW + one N-day ITW full-chain).
Tweet media one
0
4
39
@buptsb
1377 High-yield Nukes
1 year
v8ctf m128 confirmed as an 0day
Tweet media one
0
0
22
@xvonfers
xvonfers
8 hours
upd: 9 v8ctf submissions have been confirmed (three of which are 0-day), two 0-days ITW & one N-day ITW full-chain.
@xvonfers
xvonfers
13 days
upd 8 v8ctf submissions have been confirmed (three of which are 0-day), two 0-days ITW & one N-day ITW full-chain.
0
0
5
@0xP0ch1ta
Manas Ghandat
12 days
Recently, I exploited CVE-2025-2135, which was also used in v8ctf. Any feedback is highly appreciated.
0
0
0
@tchght
ttt
2 years
I am so excited , finally, I got 2nd blood of v8ctf, wait to comfirm, my exp need to brute, but i will write a writeup to prove I can increase its success rate!
Tweet media one
2
1
60
@buptsb
1377 High-yield Nukes
1 year
Another parser bug, utilized by someone in v8ctf M127
Tweet media one
@darkfloyd1014
Mr. Anthony 安東尼
1 year
Submitted a bug but it is duplicate, move ahead. Here is the fix. Our newly developed mutators are alright . @wwkenwong.
0
3
18
@insu_yun
INSU YUN
2 years
Confirmed! My student, Haein Lee, has successfully completed the 3rd submission for v8ctf! He uses a 1-day bug, and his exploit is very interesting! I hope that we can disclose the details of this exploit in the short future.
Tweet media one
2
18
179
@binitamshah
Binni Shah
1 year
From the Vulnerability to the Victory : A Chrome Renderer 1-Day Exploit’s Journey to v8CTF Glory : (Slides)
Tweet media one
Tweet media two
0
16
63
@_tsuro
stephen
2 years
The first #v8CTF submission is in \o/. This was
Tweet media one
2
23
133
@buptsb
1377 High-yield Nukes
2 years
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.
Tweet media one
@buptsb
1377 High-yield Nukes
2 years
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.
Tweet media one
1
0
4
@0x10n
Xion
1 year
compensating with the quickest v8ctf submission in history :)
Tweet media one
@0x10n
Xion
1 year
Oh no just seen a commit fixing a bug that I immediately recognize, why did I not analyze this one step further 🥲.
2
6
58
@typhooncon
TyphoonCon🌪️
1 year
🌪️ Now at #TyphoonCon24: From Vulnerability to Victory: A Chrome Renderer 1-Day Exploit's Journey to v8CTF Glory by Haein Lee
Tweet media one
1
7
47
@buptsb
1377 High-yield Nukes
1 year
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
@xvonfers
xvonfers
13 days
0-day exploited in v8ctf.
@xvonfers
xvonfers
21 days
🤔
Tweet media one
1
2
48
@buptsb
1377 High-yield Nukes
1 year
CVE-2024-2887 WebAssembly type confusion PoC Missed out on the v8ctf bounty again because I have absolutely no idea how to achieve v8 sbx escape. 🥹.
3
19
106
@xvonfers
xvonfers
4 months
v8ctf enjoyer:
Tweet media one
@xvonfers
xvonfers
4 months
😅.[395895382][turbofan].". can be exploited to force TF into reading and writing at attacker controlled locations (outside SB) when replacing node's inputs based on this corrupted arity".
1
2
28
@xvonfers
xvonfers
13 days
upd 8 v8ctf submissions have been confirmed (three of which are 0-day), two 0-days ITW & one N-day ITW full-chain.
@xvonfers
xvonfers
2 months
upd.7 v8ctf submissions have been confirmed (two of which are 0-day), still only one 0-day ITW & one N-day ITW full-chain.
0
0
6