> An attack vector might look like: You skipped over the step actually writing an exploit for this. This is some typical memory corruption. Exploiting these o

> An attack vector might look like: You skipped over the step actually writing an exploit for this. This is some typical memory corruption. Exploiting these on any modern-day system isn't as straightforward as it was in the past. With ASLR and other mitigations you usually need some form of memory leak to find out about addresses. But even if you have that you need some way for your exploit to know about the leaked address. Most exploits that do this involve some form of scripting (the most common being browser-based exploits written in javascript). I have no idea how you would pull that off in a README file.