Comment 6 for bug 1336207

Right, I didn't mean to imply that this is the same bug as described in 1184041, merely that the vulnerability is similar enough for us to reuse some of the same impact analysis wording when publishing a security advisory.