Windows Versions 7 to 10 vulnerable to Hot Potato exploit by Hackers
The Popular operating System is under the shadow of hackers, as Windows versions 7, 8, 8.1, and 10, along with Server 2008 and Server 2012, are more vulnerable to Hot Potato exploits, which allows hackers to gain complete control of your computer. Foxglove Security researchers have found that approximately all new versions of Window’s operating system are vulnerable to this exploit. By combining a group of well-known Windows security flaws, researchers also claimed to have found a way to break Windows Versions from 7 to 10 along with Windows 2008 and 2010 Server. According to FoxGlove Researchers, they named this exploit Hot Potato. Hot Potato depends on three different kinds of attacks. The attacks were first discovered at the beginning of the year 2000. Hackers bind these jointly, allowing them to remotely access the computers with Windows 7 to 10 operating systems. These exploits were discovered in the year 2000, but still, these exploits were not patched by Microsoft. With the Solution of fixing them, Microsoft would productively break compatibility between distinct versions of Windows.
What is Hot Potato?
Hot Potato combines three different security issues with Window’s OS. The Spoofing technique is highly effective with the flaw present in local NBNS abbreviated as NetBIOS Name Service. Dominant hackers can utilize this flaw to falsify WPAD, abbreviated as Web Proxy Auto Discovery Protocol, and proxy servers. Using these exploits in a chained way permits the hacker to access your computer by raising an application’s permission from the lowest range to system-level privileges. Foxglove Researchers also uploaded videos showing evidence of breaking Windows in versions 7, 8, and 10 along Windows server 2008 and 2012, respectively, to show the concept of this exploit. So this was all about the vulnerability of windows versions to hot Potato exploits by hackers. You also learned how the carelessness of Microsoft gave rise to this flaw. If Microsoft had fixed this bug earlier in 2000, this vulnerability would not have been possible. We hope you liked this article; feel free to share this with your friends.
