This CVE is a duplicate and should not be used. It was a reservation that was later merged into CVE-2017-16227. Any information or potential vulnerabilities initially associated with this CVE are now contained within CVE-2017-16227. Therefore, there is no active threat associated with CVE-2017-1000435.