News for hackers. Stuff that matters.
Re:Exploiting a Go Binary by tptacek on Thursday May 16, 2013 @10:02AM (#5718640)
Odd code like that will crash your executable, and may set up the conditions for some other exploit, but this one requires the code to be very specifically written to maliciously overwrite a function pointer.
Re:Exploiting a Go Binary by pcwalton on Thursday May 16, 2013 @11:13AM (#5719018)
What if, instead of a function pointer, an interface happened to be at that address? Given that interfaces are extremely common in Go, it seems plausible to me that many addresses in the heap could contain interfaces (and if they don't, then it may be possible to manipulate an application to create many interfaces so that they do). An attacker could overwrite the vtable pointer to point to attacker-supplied memory, and then an indirect call through the vtable could jump to shellcode.
Re:Exploiting a Go Binary by tptacek on Thursday May 16, 2013 @11:26AM (#5719103)
Sure, that's a plausible vulnerability concept for Go. Someone just has to find a way to do that. :)