https://www.bencode.io/tags/cybersec/ Recent content in Cybersec on Benny Simmonds Hugo -- 0.149.1 en-us Sun, 04 Jul 2021 21:25:37 +0000 https://www.bencode.io/posts/binhunt/ Sat, 29 May 2021 22:46:47 +0000 https://www.bencode.io/posts/binhunt/ <p>An academic paper I authored in May 2019, as part of studying <em>Reverse Engineering</em> at UNSW.</p> <h1 id="abstract">Abstract</h1> <p>Extracting meaningful semantic differences between software binaries without source code is difficult. This is a challenging problem due to the overwhelming amount of syntactic noise that small changes can result in at the assembly level. Curiously when it comes to program semantics the &ldquo;signal from the noise&rdquo; can be distilled in a manner that is both static and processor agnostic, through the application of control flow and graph isomorphism analysis, symbolic execution and theorem proving. The graph isomorphism problem has no known polynomial time algorithm (i.e. is NP) making brute force approaches computationally infeasible. By blending various static analysis techniques and applying some generalisations, consider a novel approach to overcoming the computationally infeasibility of this problem domain with a view to binary difference analysis.</p> https://www.bencode.io/posts/heap/ Sat, 19 Oct 2019 18:31:14 +1000 https://www.bencode.io/posts/heap/ <p>An academic paper I authored in October 2019, as part of studying <em>Modern Exploit Development</em> at UNSW.</p> <h1 id="abstract">Abstract</h1> <p>Heap oriented exploits continue to be an ongoing threat, and have gained popularity post the stack smashing frenzy of the 90&rsquo;s and early 00&rsquo;s. Even so called safe languages (e.g. JavaScript, Java) remain vulnerable due to their underlying C/C++ implementations. Heap allocator designs and implementations, of which there are many, struggle to strike the balance between performance and security, performance often winning out to keep programs running as fast as possible. Two ingredients are needed for a successful heap exploit, the first a memory management error in the target program, and second an exploitable heap allocator implementation. Many countermeasures in mainstream allocators seen to date are often the result of knee-jerk reactions to exploits of the past, with patching occurring to existing designs. A large body of research exists around detecting, preventing or mitigating heap attacks.</p>