Well first of all it's a HTTP response. I can see it in the file you linked too. It's also probably not from 8ch itself, considering the completely different headers it gives.
It's not aligned with any byte boundary in the file (starting at 0x37F), supporting your argument for a buffer overrun. However I'm not sure what you mean by 1452 bytes. The file is made up of 895 bytes before the HTTP header, and then that exact same 895 bytes after it.
In my opinion, you're not going to find out how this happened unless you figure out where the HTTP response came from.
On the bright side, it actually plays fine once you remove the HTTP header and all the bytes before it, file related.