This should probably be posted to oss-sec along with the CVE (CVE-2015-5271) it was assigned now the bug has been opened.
This should probably be posted to oss-sec along with the CVE (CVE-2015-5271) it was assigned now the bug has been opened.