Samuel Groß (@5aelo) 's Twitter Profile
Samuel Groß

@5aelo

V8 Security technical lead. Previously Project Zero. Personal account. Also @[email protected] and saelo.bsky.social

ID: 1452156612

linkhttp://www.phrack.org/author_saelo.html calendar_today23-05-2013 18:20:02

758 Tweet

24,24K Takipçi

499 Takip Edilen

stephen (@_tsuro) 's Twitter Profile Photo

We just started the #v8CTF: a new exploit bounty program for v8! * $10,000 * N-day vulnerabilities are in scope, but limited to first submission per deployed v8 version * unlimited for self-found bugs (on top of regular VRP) More info here: github.com/google/securit…

Samuel Groß (@5aelo) 's Twitter Profile Photo

Some really cool recent work by stephen: * We now have a V8 exploit bounty ($10k) in the form of the V8CTF: github.com/google/securit… * A blog post about our CFI plans: v8.dev/blog/control-f…

matteo malvica ⭕ (@matteomalvica) 's Twitter Profile Photo

Venturing into the world of browser exploitation? these two Samuel Groß's Phrack articles are an essential rite of passage 👇🌐 phrack.org/issues/70/3.ht… phrack.org/issues/70/9.ht…

Samuel Groß (@5aelo) 's Twitter Profile Photo

I've been meaning to write this for some time now and finally got around to it: a "V8 Sandbox Glossary" document that briefly explains the most important terms/concepts used for the sandbox and links to the respective design documents: docs.google.com/document/d/10Z…

stephen (@_tsuro) 's Twitter Profile Photo

The first #v8CTF submission is now public: bughunters.google.com/reports/vrp/38… Note that the current flag is still up for grabs, maybe M118 is unhackable? ;P You should also check out @madstacks3's excellent writeup at madstacks.dev/posts/Start-Yo…

Samuel Groß (@5aelo) 's Twitter Profile Photo

Some early performance numbers for the V8 Sandbox: looks like with most of the performance critical parts in place now, the overall performance cost of this future security boundary is only around 1% on popular benchmarks \o/ More results are linked from chromium-review.googlesource.com/c/v8/v8/+/5206…

Some early performance numbers for the V8 Sandbox: looks like with most of the performance critical parts in place now, the overall performance cost of this future security boundary is only around 1% on popular benchmarks \o/

More results are linked from chromium-review.googlesource.com/c/v8/v8/+/5206…
Samuel Groß (@5aelo) 's Twitter Profile Photo

New V8 Sandbox design document is out: docs.google.com/document/d/12M… This discusses how a hardware-based sandbox instead of the currently purely software-based one might look like in a somewhat distant future (if at all)

Samuel Groß (@5aelo) 's Twitter Profile Photo

Big day for the V8 Sandbox: * Now included in the Chrome VRP: g.co/chrome/vrp/#v8… * Motivation & goals discussed in a new technical blog post: v8.dev/blog/sandbox If there is ever a Sandbox "beta" release, this is it!

Samuel Groß (@5aelo) 's Twitter Profile Photo

Finally got around to publishing the slides of my talk offensivecon from ~two weeks ago. Sorry for the delay! The V8 Heap Sandbox: saelo.github.io/presentations/… Fantastic conference, as usual! :)

Samuel Groß (@5aelo) 's Twitter Profile Photo

Another big step towards becoming a security boundary: today we’re expanding the VRP for the V8 Sandbox * No longer limited to d8 * Rewards for controlled writes increased to $20k * Any memory corruption outside the sandbox now in scope bughunters.google.com/about/rules/ch… Happy hacking!

Carl Smith (@cffsmith) 's Twitter Profile Photo

I’m very excited to announce that we at V8 Security have finally published our first version of Fuzzilli that understands Wasm! Go check it out at github.com/googleprojectz…. While we still have a way to go in improving it, we think it shows a promising approach!

xvonfers (@xvonfers) 's Twitter Profile Photo

Thanks to these articles from Samuel Groß(Samuel Groß), I started studying browsers vr/xd and this was basically the starting point: phrack.org/issues/70/3#ar… phrack.org/issues/70/9#ar…