This issue was confirmed by Nozomi Networks after a bug reported by one of our Customers.

2 vulnerability records and advisories credit this contributor.