Comment 2 for bug 1603292

This looks like it was probably switched from Public to Public Security on accident, so I'm setting it back to Public now.

In the future, if switching a bug from Public to Public Security (indicating that it represents a report of a suspected security vulnerability), please accompany that with an explanation of the security risks represented... ideally along with a reasonable attack scenario.