Remind me why proprietary software is safe again, Sup Forums
>CVE-2017-11779 fixed by Microsoft in October of 2017, covers multiple memory corruption vulnerabilities in the Windows DNS client. The issues affect computers running Windows 8/ Server 2012 or later, and can be triggered by a malicious DNS response. An attacker can exploit this issue to gain arbitrary code execution in the context of the application that made the DNS request.
>This means that if an attacker controls your DNS server (e.g., through a Man-in-the-Middle attack or a malicious coffee-shop hotspot) – they can gain access to your system. This doesn’t only affect web browsers – your computer makes DNS queries in the background all the time, and any query can be responded to in order to trigger this issue.
>only in Windows 8 and Windows server 2012 Why is this relevant? Windows 8 is five years old.
Logan Long
Are you unable to read?
>The issues affect computers running Windows 8/ Server 2012 or later >or later
>These vulnerabilities affect all versions of Windows from Windows 8 / Windows Server 2012 through Windows 10 / Windows Server 2016. Versions of Windows prior to this are not vulnerable.
Jeremiah Brooks
>remote code injection bug has existed in the wild for five years Windows users will defend this.
Elijah Brooks
It clearly says that it affects all versions from Windows 8/Server 2012 up to Windows 10/Server 2016
Cooper Miller
>running Windows 8/ Server 2012 or later Lol, hhahahahahhahahaha
Elijah Cox
I fucking knew the safe bet was to remain on 7. I knew it!
Andrew Brooks
Lol I'm using 7 which makes me safe.
Ian Jones
>Lol I'm using 7 which makes me safe. So does installing the patch tbqh.
Jaxson James
Heartbleed, freetard.
Luis Bailey
How shit must the pajeets working at Microsoft be at code validation and reviewing, if it's preferable to run a six year old kernel with known security issues rather than installing newer versions with unknown security issues?
Alexander Baker
>accident
Matthew Jenkins
1) Heartbleed was not in the wild for so long 2) Heartbleed was a library issue, alternative SSL implementations to OpenSSL existed then and exists now 3) Hearbleed didn't allow fucking remote code injection running in ring 0
All your systems may be compromised without you even knowing it.
Jeremiah Wright
>Windows Found your problem
Elijah Price
>All your systems may be compromised without you even knowing it. Then shut the fuck up.
Hunter Torres
>Angry and confused Windows user lashing out
Benjamin Robinson
>Then shut the fuck up Why? You it's imperative that everyone running Windows 8 or newer install the security patch ASAP.
Elijah Gray
>Windows toddler can't read
>Windows toddlers think running archaic and EOL'd versions of Windows make them safe
>Windows toddler is unable to understand the severity of this vulnerability compared to other vulnerabilities
>Windows toddler think just shutting up about the issue makes it go away
Windows toddlers on suicide watch.
Blake Russell
This is actually quite bad.
Luis Bell
>Windows 8 and Windows server 2012
Carter Torres
And everything newer.
Kayden Bell
>Windows toddlers think running archaic and EOL'd versions of Windows make them safe kek, winblows 7 has been vulnerable since beta.
Benjamin Bell
I don't understand why Microsoft would publicly announce this, rather than just fixing it silently. Doesn't announcing it make it known to potential exploiters, who can then target systems that aren't easily updated? What's Microsoft's reasoning behind going public with this?
Sebastian Russell
This. Showing vulnerabilities to everyone is why I will never use an open source system. It's just shooting yourself in the foot.
Kayden Rogers
The Apple Macbook Pro with Retina Display doesn't have this problem.
Carter White
It does if it got Windows 8 or newer installed.
Elijah Carter
I gotta wonder what it's like to buy an overpriced laptop like that where one of the selling points is the OS that it includes and install an OS that is supported on any other laptop in the market
