←
Alex Rebert119 posts
Alex Rebert avatar

Alex Rebert

@ayper

Security @ Google. Previously co-founder of @ForAllSecure. Opinions here are my own. @ayper@infosec.exchange

◷ Joined August 2008▧ 5 Photos and videos
Zardus@DEFCON.social avatar
⟳ Alex Rebert retweeted
Zardus@DEFCON.social@Zardus·Apr 28

Can we translate all C to Rust? The susceptibility of C to memory corruption has long been a cybersecurity pain point, and coding agents can free us of it. Read on for my recent experiments in this space, and apt & docker repos that you can pull rust-converted libraries from!

Heather Adkins - Ꜻ - Spes consilium non est avatar
⟳ Alex Rebert retweeted
Heather Adkins - Ꜻ - Spes consilium non est@argvee·12 Nov 2025

Hardening the C++ Standard Library at massive scale. A look at increasing memory safety with libc++ hardening — a collaborative paper from engineers at Apple and Google. The results have been impressive: at Google the team discovered and fixed 1000+ bugs as hardening was enabled. queue.acm.org/detail.cfm?id=…

Google VRP (Google Bug Hunters) avatar
⟳ Alex Rebert retweeted
Google VRP (Google Bug Hunters)@GoogleVRP·21 Jan 2025

🛡️Want to help make the open source world safer and earn up to $45k 💰? We've revamped our Patch Rewards Program, extending its scope and increasing rewards for security patches – with a particular focus on memory safety, including bonus multipliers! bughunters.google.com/blog/5…

Google VRP (Google Bug Hunters) avatar
⟳ Alex Rebert retweeted
Google VRP (Google Bug Hunters)@GoogleVRP·4 Dec 2024

Celebrating 15 years of password hacking 💻 🔑, Swiss Army knives (and sometimes even chainsaws or swords) included! 😲 Discover how Google's security teams turn employee farewells into security tests. bughunters.google.com/blog/6…

Kinuko Yasuda avatar
⟳ Alex Rebert retweeted
Kinuko Yasuda@kinu·16 Nov 2024

Bounds-checking in C++: so people ask if the .3% overhead is real. It's not just a benchmark result, we got this through our Google-Wide profiling, that gives us the live insights from DCs. This surprised us too as it was much cheaper than we thought research.google/pubs/google-…

Excited to share our latest post on memory safety! We're tackling spatial safety in our massive C++ codebase by hardening libc++ *by default*. It adds bounds checks to things like std::vector, preventing a fair bit of out-of-bounds vulnerabilities: security.googleblog.com/2024…

Alex Rebert avatar
Alex Rebert@ayper·15 Nov 2024

The best part? It's incredibly cost-effective, with an average performance overhead of just 0.30%.  So there's really no reason not to do it if you're running C++ code :)

Alex Rebert avatar
Alex Rebert@ayper·15 Nov 2024

This improves spatial memory safety across Google's services, including performance-critical components of Search, Gmail, Drive, YouTube, and Maps.  We've already seen it disrupt a red team exercise, reduce segfaults by 30%, and improve code correctness.

Alex Rebert avatar
Alex Rebert@ayper·15 Nov 2024

Excited to share our latest post on memory safety! We're tackling spatial safety in our massive C++ codebase by hardening libc++ *by default*. It adds bounds checks to things like std::vector, preventing a fair bit of out-of-bounds vulnerabilities: security.googleblog.com/2024…

Lukas Weichselbaum avatar
⟳ Alex Rebert retweeted
Lukas Weichselbaum@we1x·22 Oct 2024

The dedication and hard work has payed off: "for hundreds of complex web applications that are built on Google’s hardened and safe-by-design frameworks, we've averaged less than one XSS report per year in total" (see page 9 of the whitepaper).

Secure by design takes dedication and years of hard work to get the balance right between velocity and safety. Read a bit about @Google’s commitment and journey in our new white paper. Humbled to work with the professionals that make this happen everyday. blog.google/technology/safet…

Deirdre Connolly¹ avatar
⟳ Alex Rebert retweeted
Deirdre Connolly¹@durumcrustulum·15 Oct 2024

Percentage of codebase that's memory-safe 📈, memory-safety vulns 📉, EVEN IF YOU KEEP ADDING LINES OF C 🤯

NEW EPISODE! You may not be rewriting the world in Rust, but if you walk like the Android team, you'll drive down your memory-unsafety vulnerabilities more than 2X below the industry average over time! 🎉 securitycryptographywhatever… youtu.be/WL4CgVI6p9g

Alex Rebert avatar
Alex Rebert@ayper·15 Oct 2024

Excited to share Google's memory safety strategy! We're working to build safer software by migrating to memory-safe languages like Rust as well as hardening our existing C++: security.googleblog.com/2024…. We'll be sharing more details in upcoming posts.

Alex Rebert avatar
Alex Rebert@ayper·4 Oct 2024

Google CVR is doing incredible vulnerability research.

Learn how Google CVR could have potentially exfiltrated Gemini 1.0 Pro before launch last year. We describe the vulnz, the fix, and tips for bughunters. Also, shout-out to @epereiralopez for teaming up to adapt this work to another cloud provider. bughunters.google.com/blog/5…

tylerni7 avatar
⟳ Alex Rebert retweeted
tylerni7@tylerni7·24 Sep 2024

Released a blog about our @theori_io AIxCC experience! medium.com/@sa-blog/winning-… @tjbecker and I were hoping to have more info about other challenges, but they aren't released, so some of the information is a bit limited. Still, hope folks can enjoy reading it!

Alex Rebert avatar
Alex Rebert@ayper·25 Sep 2024

The drop in Android's memory safety vulnerabilities is astonishing. It's counterintuitive, but prioritizing memory-safe languages in new code quickly reduces memory-safety risks. Once we turn off the tap of new vulnerabilities, they start decreasing exponentially.

I’m super excited about this blogpost. The approach is so counterintuitive, and yet the results are so much better than anything else that we’ve tried for memory safety. We finally understand why. security.googleblog.com/2024…