It looks like a minor bug that was reported as a high severity security issue, with the reporter not being able to explain why other than "this kind of error CAN be bad".
Not sure if I'd be snarky for the first few clueless reports, but I'd probably be getting there after several of them have happened.
Not sure if I'd be snarky for the first few clueless reports, but I'd probably be getting there after several of them have happened.