Tim Willis retweeted
Some personal news: I'm thrilled to be moving back to Project Zero! Specifically I'll be joining the Big Sleep project to find vulnerabilities in JavaScript engines. We've already found and reported our first vulnerability in V8 last week: issuetracker.google.com/issu…
Tim Willis retweeted
If you've been keeping track on the Big Sleep bug tracker at goo.gle/bigsleep you might have noticed it lists more bugs now compared to last week. Including a "High impact issue in V8" :)
That time when @tehjh was just reviewing a new Linux kernel feature, found a security vuln, then went on a journey to see if he could exploit it from inside the Chrome Linux Desktop renderer sandbox (spoiler: very yes)
googleprojectzero.blogspot.c…
Tim Willis retweeted
Today @Google Project Zero announced a new trial policy: Reporting Transparency. We’ll now share when we report a security vuln to a vendor within 1 week including products + deadlines. Goal: shrink the patch gap + drive faster, safer updates for users: googleprojectzero.blogspot.c…
Great to see this live!
Let's see how the trial pans out 🍿👀
While most vendors ship timely patches for vulnerabilities reported by Project Zero, they don’t always reach users. Today, we’re announcing Reporting Transparency, a new policy to encourage downstream fixes
googleprojectzero.blogspot.c…
Part 7 (!) of @j00ru's Windows Registry adventure is now live:
googleprojectzero.blogspot.c…
"I will describe the various areas that are important in the context of low-level security research... all possible entry points to attack the registry... and the primitives they generate"🙌
For those that won't be in Germany next weekend to see @dillon_franke live, this is the next best thing!
(post also includes Dillon's fuzzing harness and tools Dillon built along the way) 🎉
Thrilled to announce my new Project Zero blog post is LIVE! 🎉 I detail my knowledge-driven fuzzing process to find sandbox escape vulnerabilities in CoreAudio on MacOS.
I'll talk about this and the exploitation process next week @offensive_con!
googleprojectzero.blogspot.c…
...and now, introducing Part 6 of @j00ru's work on the Windows Registry:
googleprojectzero.blogspot.c…
📖👀
Part 5 of @j00ru's Windows Registry Adventure is out!
googleprojectzero.blogspot.c…
Incredible depth of knowledge on display, and good to see it shared as a reference with the world ❤️
Two new posts from @tiraniddo today:
googleprojectzero.blogspot.c… on reviving a memory trapping primitive from his 2021 post.
googleprojectzero.blogspot.c… where he shares a bug class and demonstrates how you can get a COM object trapped in a more privileged process.
Happy Reading! 📚
It doesn't happen very often, but Project Zero is hiring!
goo.gle/41DBQBY
Please share with anyone you think would be awesome for the role 🎉
Looking for at least one person. DMs open if you want to reach out about the role.
The team: youtu.be/My_13FXODdU
Part 5 of @j00ru's Windows Registry Adventure is out!
googleprojectzero.blogspot.c…
Incredible depth of knowledge on display, and good to see it shared as a reference with the world ❤️
Tim Willis retweeted
Great to see Apple quickly patch the MacOS sandbox escape/privilege escalation vulnerability I reported to them. Big thanks to @NedWilliamson, @i41nbeer, and @i41nbeer for all the help :) I'm working on a blog post and hope to release it soon!!
Tim Willis retweeted
My blog post is now live alongside @amnesty 's joint release, providing remarkable insight into an ITW exploitation campaign!
googleprojectzero.blogspot.c…
Turns out that you can find out quite a bit with just some kernel stacktraces ;)
From Amnesty:
securitylab.amnesty.org/late…
If you've ever wondered if one can determine a vuln from just the kernel panic logs, @__sethJenkins (feat. @tehjh & @benoitsevens) have something to share: googleprojectzero.blogspot.c…
Great to collaborate with @amnesty, find vulns and get them fixed: securitylab.amnesty.org/late…
Finding 0day is not the most impactful thing that Project Zero does 😲 — it's sharing knowledge 🧠. One part of that sharing is our tooling work to help other devs and reserachers.
Today's installment, @tiraniddo's updated OleView.NET👍
Blog: googleprojectzero.blogspot.c…
Project Zero Blogpost recap for the month:
googleprojectzero.blogspot.c… — @j00ru doing another deep dive into the Windows Registry
googleprojectzero.blogspot.c… — Nick Galloway's dav1d fuzzing case study
(new) googleprojectzero.blogspot.c… — an update on using LLMs to find vulns
Enjoy! 🎉
"While... public and in-the-wild research on Android GPU drivers [exists], other chipset components may not be as frequently audited so this research sought to explore those drivers in greater detail."
Hot tip: There's a video version and a proof of concept exploit at the end👍
My new Project Zero blog post, Driving Forward in Android Drivers is live! 🥳
googleprojectzero.blogspot.c…
Join @j00ru as he shares his research/adventure through the Windows Registry:
googleprojectzero.blogspot.c…
50 CVEs is just the beginning. Future posts will explore the attack surface, history, practical exploitation using hive memory corruption, cell indexes and other good times🎉
Great to see srldf.org working as intended!
This fund would have never launched without the hard work of many, but a special shoutout to @HarleyGeiger and @charley_snyder_ to making srldf.org a reality.
Shout out to the Security Research Legal Defense Fund for helping us go public about our train research! We're honored to be their first grantees.
Longer post + link to their announcement: social.hackerspace.pl/@q3k/1…
New Project Zero blogpost by Mark Brand - first mobile device ships with MTE (and how to enable it).
"MTE on a production handset for the first time is a big step forward... there's real potential to use this technology to make 0-day harder".
googleprojectzero.blogspot.c…











