1 matches found
CVE-2016-3919
CVE-2016-3919 is rejected/not used and does not represent an active vulnerability; reference CVE-2016-5195 instead.