Qrious Secure (@qriousec) 's Twitter Profile
Qrious Secure

@qriousec

ID: 1596192604915642369

linkhttp://qriousec.io calendar_today25-11-2022 17:22:37

8 Tweet

633 Followers

3 Following

Qrious Secure (@qriousec) 's Twitter Profile Photo

Additionally, last year our teammate Bien 🇻🇳 also pwned Linux kernel on kernelCTF with a 0-day, that has been fixed and assigned CVE-2023-4244. So far, we have successfully pwned 2/3 liveCTF hosted by Google. We are going to aim for kvmCTF in the future.

Additionally, last year our teammate <a href="/bienpnn/">Bien 🇻🇳</a> also pwned Linux kernel on kernelCTF with a 0-day, that has been fixed and assigned CVE-2023-4244.
So far, we have successfully pwned 2/3 liveCTF hosted by Google.
We are going to aim for kvmCTF in the future.
Suto (@__suto) 's Twitter Profile Photo

I successfully exploited #V8ctf using CVE-2024-0517, writeup and exploit will be published later. chromereleases.googleblog.com/2024/01/stable…

Qrious Secure (@qriousec) 's Twitter Profile Photo

CVE-2024-0517 - Chrome V8 maglev compiler optimization RCE vulnerability, has been derestricted (along with exploit code). This was reported by our teammate Suto issues.chromium.org/issues/41488920

CVE-2024-0517 - Chrome V8 maglev compiler optimization RCE vulnerability, has been derestricted (along with exploit code). This was reported by our teammate <a href="/__suto/">Suto</a>
issues.chromium.org/issues/41488920
Qrious Secure (@qriousec) 's Twitter Profile Photo

After CVE-2024-0223, we reported the bypass and it was assigned CVE-2024-3516: issues.chromium.org/issues/3288591… Months later, someone else reported another variant and Google decided to give up and allow Chrome's GPU to crash instead of fixing the issue.

After CVE-2024-0223, we reported the bypass and it was assigned CVE-2024-3516:
issues.chromium.org/issues/3288591…
Months later, someone else reported another variant and Google decided to give up and allow Chrome's GPU to crash instead of fixing the issue.