Yes, that is the exact same issue. While searching for any prior art, i did not find your blog post, but the problem seemed far too obvious for me to be the only one to have ever stumbled upon it. I do think this issue needs some exposure, there seem to be a lot of potential security ramifications.