The point the article is making is that this is a 2017 vulnerability and is still present on the lastest release of Windows 10