Collaborate Disseminate
I’m trying to learn about heap exploitation with vulnerable Linux binaries. I’m currently working through the binaries on hack the box and I realized these binaries were compiled with older versions of libc (no tcache).
Sometimes debugging just doesn’t go the way you want it to. When USB problems arise, you can usually use a protocol analyzer to find the issue causing trouble. For [Paul Stoffregen], it was only the first step in a long process to find the culprit.
The complaint that …read more
Ihave intermediate file during x32dbg processing with some unknown format. The few starting bytes of encoded file is:
2E 08 31 5F 63 52 A1 5F 2D 08 31 5F 2A 08 31 5F D1 F7 31 5F 96 08
31 5F 2E 08 31 5F 6E 08 31 5F 2E 08 3… Continue reading Which decoding is used by x32dbg durring debuging a file?
The very good security recommendation is: the mobile app should check if the developer mode is turned on and it should not start. Both in android and iOS. Do you agree with this sentence? What the development mode is threate… Continue reading Is the developer mode like the opened door for hackers to debug the mobile app?
Frameworks for web apps typically can run in either production mode or development mode. One of the major differences between the two modes is how exceptions are handled: in development mode the browser will typically be sent… Continue reading What is the use of disabling detailed exception pages on open-sourced apps?
Does GHIDRA have a debugger attached for dynamic analysis of application?
Firmware and software are both just code, right? How different could the code that runs Internet-scale distributed web stuff be from the code that runs a tiny microcontroller brain inside a personal hydroponics device? Night and day!
Ruth Grace Wong works in the former world, but moonlights as a manufacturing …read more
Continue reading Supercon: Ruth Grace Wong and Firmware From the Firehose
Let’s be honest, no one likes to see their program crash. It’s a clear sign that something is wrong with our code, and that’s a truth we don’t like to see. We try our best to avoid such a situation, and we’ve seen how compiler warnings and other static code analysis tools can help us to detect and prevent possible flaws in our code, which could otherwise lead to its demise. But what if I told you that crashing your program is actually a great way to improve its overall quality? Now, this obviously sounds a bit counterintuitive, after all …read more
Continue reading Crash your code – Lessons Learned From Debugging Things That Should Never Happen™
I am doing this reverse engenering challenge. I woudl like to execute it on Windows with radare2 because it’s a PE application but I collected this informations on my ubuntu radare2 installation before trying to execute it.
T… Continue reading Change flag comparaison with radare2
We’ve all been there. When debugging a microcontroller project, we just want to put in a print statement to figure out what’s going on with the microcontroller in real time. However, advanced embedded programmers know that printf statements are verboten: they’re just too SLOW. While not fixing this plight entirely, [Atakan Sarioglu] has come up with a clever way to create readable debug messages with minimal runtime overhead.
[Atakan Sarioglu]’s innovation, called BigBug (Github), is a dynamically-generated codebook. The codebook translates abbreviated messages sent over serial (UART here) to longer-form human-readable messages. To generate the codebook, BigBug automatically parses your …read more
Continue reading “DB” = Abbreviated Microcontroller Debugging