On the blog itself,

"Given the recent attention to this post, we’ll release the 2nd part very soon. It details a workaround for this bug, again, not a vulnerability."


Doesn't sound like much of an issue to me and perhaps why Microsoft isn't too worried about fixing it.