Comment 6 for bug 2048106

Thanks for checking. Since we didn't treat bug 1842749 as a vulnerability, and the risks for this are the same or a subset of that report, we should proceed in a similar fashion with this report as well. I'll switch it to public now.