pwndbg's profile picture.

pwndbg

@pwndbg

pwndbg reposted

Kind of neat to watch @Pwntools grow over time. @disconnect3d_pl is setting up ReadTheDocs for @pwndbg so I took a look at statistics for docs.pwntools.com… It’s a bit humbling to see so many people using the project and using the documentation!

ebeip90's tweet image. Kind of neat to watch @Pwntools grow over time.  @disconnect3d_pl is setting up ReadTheDocs for @pwndbg so I took a look at statistics for docs.pwntools.com… 

It’s a bit humbling to see so many people using the project and using the  documentation!

pwndbg reposted

Glad to see people using @Pwndbg (“makes debugging with GDB suck less”) for actual browser RCE + SBX escape chains! If you’re curious, check out pwndbg.com and join our Discord! discord.gg/x47DssnGwm Oblig respect for GEF too! / cc @_hugsy_

discord.com

Join the pwndbg Discord Server!

Server for Pwndbg users and development. Pwndbg is a plugin to GDB for reverse engineering and exploit development | 906 members

I completely underestimated how much harder heap grooming is on thread-caching memory allocators. Not the most reliable exploit tbh, likely needs better heap-spraying primitives. Still, I'm satisfied for a first contact to chrome RCE+SBX chains. Write-up sometime soon

ulexec's tweet image. I completely underestimated how much harder heap grooming is on thread-caching memory allocators. Not the most reliable exploit tbh, likely needs better heap-spraying primitives. Still, I'm satisfied for a first contact to chrome RCE+SBX chains. Write-up sometime soon


@Pwndbg being used for real browser exploitation + SB escape⁉️ Shout out to @disconnect3d_pl, @anthraxx42, @arusekk and all the other contributors for keeping the Pwndbg community alive and thriving! We’re always looking for new ideas and pull requests! pwndbg.com

I completely underestimated how much harder heap grooming is on thread-caching memory allocators. Not the most reliable exploit tbh, likely needs better heap-spraying primitives. Still, I'm satisfied for a first contact to chrome RCE+SBX chains. Write-up sometime soon

ulexec's tweet image. I completely underestimated how much harder heap grooming is on thread-caching memory allocators. Not the most reliable exploit tbh, likely needs better heap-spraying primitives. Still, I'm satisfied for a first contact to chrome RCE+SBX chains. Write-up sometime soon


pwndbg reposted

To prep for @oooverflow’s challenges at @defcon finals, have a REVERSING 500 challenge that I created several years ago. I’ve never seen a write-up for it, and would really like to see one! Pretty sure only @lokihardt has solved it. Fixed link: drive.google.com/drive/folders/…


Hello all! @Pwndbg has moved to Discord! Come join the community to learn about and help develop Pwndbg! discord.gg/x47DssnGwm We’ve also tagged a new release, 2021-06-22. More information and downloads at pwndbg.com!


pwndbg reposted

@pwntools pro-tip for an underrated feature: ELF.from_assembly(shellcraft.sh()).debug().interactive() Pops open the debugger automatically, pairs really well with @pwndbg Works for any architecture, even automates qemu-user debug stub setup!

ebeip90's tweet image. @pwntools pro-tip for an underrated feature:

ELF.from_assembly(shellcraft.sh()).debug().interactive()

Pops open the debugger automatically, pairs really well with @pwndbg 

Works for any architecture, even automates qemu-user debug stub setup!
ebeip90's tweet image. @pwntools pro-tip for an underrated feature:

ELF.from_assembly(shellcraft.sh()).debug().interactive()

Pops open the debugger automatically, pairs really well with @pwndbg 

Works for any architecture, even automates qemu-user debug stub setup!

Loading...

Something went wrong.


Something went wrong.