![]() I do not know if that is still the case so ymmv. I didn’t think about this until I’d already cleared the files, but in the “olden days” you had to specify all three “special” attributes in the command (system, hidden, and read-only) in order to add/remove any of them, so that’s why I did it that way. With the system attribute gone, I was then able to delete the files and clear the vulnerability from Nessus. Turns out that all four files had the system attribute set, so in an elevated command prompt, navigated to the folder and ran “attrib *.* -s -h -r” which removed the system attribute. Those files were quite persistent even changing permissions and ownership to Everyone did not allow them to be deleted, but did result in the fun message, “You require permission from Everyone to make changes to this file.” ![]() Adobe has even taken the step of removing download pages for Flash Player from its website, to prevent anyone curious from being tempted to install it for themselves in its last days of life. The only issue I had was that the DISM command (at least on 2016) still left the four ActiveX files under c:\windows\system32\macromed\flash intact, three of which were still triggering our Nessus scanner as critical vulnerabilities. Since Flash can potentially be a security risk, especially with no further updates on the horizon, Adobe is actively advising users to uninstall the Flash Player from their computers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |