@dronesec

researcher. exploit dev. hacking @ stripe stop using twitter. find me @ [email protected]

Portland, OR
Joined June 2012
CVE-2023-6246: Heap-based buffer overflow in the glibc's syslog(), @Qualys Security Advisory. openwall.com/lists/oss-secur…
1
15
1
17
5,122
Bryan Alexander retweeted
The Kerberos PAC verification bypass me and @monoxgas showed at the end of our BH presentation and was fixed last month is now open in the issue tracker. Certainly an interesting one :) bugs.chromium.org/p/project-…
1
34
83
Bryan Alexander retweeted
Breaking the Chrome Sandbox with Mojo - the recording of my black hat talk is out: youtu.be/qhhJCLy0YBA (I'm painfully aware of the red shift :) )
1
38
142
Bryan Alexander retweeted
Wherein I propose that C++ initialize all stack variables to zero, preventing ~10% of CVEs. Cost: none. 🔗 wg21.link/P2723R0 🔗
73
242
39
1,636
Bryan Alexander retweeted
Six actively exploited 0days patched today by Microsoft including one found by @benoitsevens & @_clem1 from TAG. duo.com/decipher/microsoft-f… 2022 and we are still seeing active IE scripting exploitation 😔 Thanks to Microsoft for the quick turnaround and patch.
1
25
59
Bryan Alexander retweeted
Now this is a pretty handy tool... "A plugin to introduce interactive symbols into your debugger from your decompiler" // by @mahal0z github.com/mahaloz/decomp2db…
Bryan Alexander retweeted
Inside Elon Musk's "free speech" Twitter, a culture of secrecy and fear has taken hold. Managers and employees have been muzzled, Slack channels have gone dark, and workers are turning to anonymous gossip apps to find out basic info about their jobs. washingtonpost.com/technolog…
103
669
199
1,788
Bryan Alexander retweeted
My new blog series: Technical Analysis of Windows CLFS Zero-Day Vulnerability CVE-2022-37969 - Part 1: Root Cause Analysis zscaler.com/blogs/security-r… Part 2: Exploit Analysis zscaler.com/blogs/security-r… #0day #exploit #vulnerability #CVE_2022_37969
1
93
3
223
Bryan Alexander retweeted
A couple months overdue, here's the open source release of Concurrence, my new fuzzing library for thread-based targets. Integration code to SockFuzzer, plus Mach process/IPC/VM/etc. support are coming soon. Check it out at github.com/googleprojectzero…
5
62
1
235
Bryan Alexander retweeted
Slides for "Sanitizing the Linux kernel: On KASAN and other Dynamic Bug-finding Tools", the talk I just gave at Linux Security Summit Europe 2022. Covers: 🐧 Generic KASAN implementation 🔥 Other Sanitizers 🗡 Extending KASAN and KMSAN to find more bugs docs.google.com/presentation…
7
75
2
254
Bryan Alexander retweeted
New blog post! Part 1 in my new PlayStation hacking series: An **unpatched** PS4 / PS5 userland exploit that also allows pirating PS2 games. mast1c0re: Hacking the PS4 / PS5 through the PS2 emulator - Part 1 - Escape: cturt.github.io/mast1c0re.ht… Video demo: youtube.com/watch?v=GIl1mR0H…
61
299
20
1,194
Bryan Alexander retweeted
We had quite some fun for the last 2.5 years fuzzing CPUs. We wrote one system, scratched it, and wrote another one. This week we open-sourced most of it, and hope to open-source more in the future. github.com/google/silifuzz
5
133
4
596
Bryan Alexander retweeted
We've finally landed the run-time memcpy() overflow warning patch in linux-next: git.kernel.org/pub/scm/linux… So now I'm constantly reloading a search on lore, checking if anyone has run into new instances on real work loads. :P lore.kernel.org/all/?q=%22de…
1
18
53
Bryan Alexander retweeted
Details about the @MDSecLabs 's process for identifying Veeam 1Day vulns, writing working exploit & considerations for further weaponisation (including preauth. RCE(s), LPE + complete analysis) - Such an awesome post by @SinSinology 👏 defense.one/d/36-cve-2022-26…
2
20
1
51