| Blog | https://disconnect3d.pl/ |
| GitHub | https://github.com/disconnect3d |
| https://twitter.com/disconnect3d_pl |
Fwiw there is an update about Anthropic's Project Glasswing: https://anthropic.com/research/glasswing-initial-update
The coordinated vulnerability disclosure program can now be seen here: https://red.anthropic.com/2026/cvd/ledger/
Example finding: https://red.anthropic.com/2026/cvd/findings/ANT-2026-TZQ1KH7E
:)
Pwndbg 2026.02.18 is out! Enhance your GDB or LLDB experience!
We visualize branches in nearpc, synchronize your decompiler (IDA/Binja/Ghidra) via decomp2dbg, annotate stack variabless from debug info or decompiler, support new Linux kernel debugging commands - for tracing SLUB allocs/frees or dumping tasks information.
See what's changed in: https://github.com/pwndbg/pwndbg/releases/tag/2026.02.18
Want Pwndbg to keep moving fast, or, having us give a talk about it? Sponsor us: https://github.com/sponsors/pwndbg/
We released new Pwndbg: https://github.com/pwndbg/pwndbg/releases/tag/2025.05.30 !
Among others it brings:
- New & improved kernel debugging commands (buddydump, msr, slab) and more x64 regs in context
- New command for dealing with armcm exceptions: dump-register-frame
- Disasm now shows an ✘ marker for emulated branches we know won't be taken
- Improved disasm for ARM, MIPS and LoongArch64 architectures
- Initial support for the IBM s390x architecture
- IDA sync integration fixes
And also cool portable one-liner installers:
$ curl -qsL 'https://install.pwndbg.re' | sh -s -- -t pwndbg-gdb
$ curl -qsL 'https://install.pwndbg.re' | sh -s -- -t pwndbg-lldb
Want to support us? Sponsor us at https://github.com/sponsors/pwndbg !
I will be giving a talk on Pwndbg open source development in ~1h on a local Python meeetup!
It will be livestreamed on: https://www.youtube.com/live/euK_S81Qnuo?si=EhZ-WhnP-4yZRElE
Released new Pwndbg: 2025.04.18
It adds display of breakpoints in the disasm view, new libcinfo command, improves attachp & hexdump commands, UI, TUI and more. Also, command names use "-" istead of "_" now for consistency.
Read more and download it on https://github.com/pwndbg/pwndbg/releases/tag/2025.04.18 !
A call to memcpy() in a single binary that uses glibc may behave in 12 different ways depending on the features of the specific x86-64 CPU you run it on.
Here is a list of those impls in glibc:
Fwiw this may matter a lot during binary exploitation. This was important in a challenge from PlaidCTF 2025. E.g. passing a negative (or: very huge) length allowed you to write past a buffer without a crash (the given implementation was not doing a wild copy).
We scored 1st place in the DiceCTF 2025 Quals cybersecurity competition with my team justCatTheFish 😼🐟 this weekend. We qualified for and will go to the finals in New York 🙂
Full scoreboard & challenges: https://ctf.dicega.ng/scores
If someone read the blog post, I edited it with two additions:
1) If the randomized address is before the main thread stack, the kernel will expand the stack memory mapping when such an address is accessed. This can be seen on the screenshot below from Pwndbg 🙂 and is explained more in the blog post (see "EDIT" for more info).
2) I added a "Why using the value of 65536?" section explaining why the `vm.mmap_min_addr` value is not e.g. 1.
Thx to MrQubo and Hackerspace Krakow for info & questions!
I have written a blog post about null pointers on Linux:
https://disconnect3d.pl/2025/03/03/when-null-isnt-null-on-linux/
