Re:Windows 10 0day exploit goes wild, and so do Microsoft ma...
by pomfpomfpomf3 on Monday February 06, 2017 @04:44AM
(#13577983)
tl;dr: a null deref in windows kernel when you connect to a malicious SMB share
[ Parent
| on HN ]
Re:Windows 10 0day exploit goes wild, and so do Microsoft ma...
by MohammadLee on Monday February 06, 2017 @07:23AM
(#13578792)
tl;dr: a CVSS 7.8 Windows vulnerability in the SMB service can allow an attacker to DoS any machine with the filesharing service exposed; the possibility of RCE seems to have been discarded; exploits are freely available online. This article complains that Microsoft's communication is lacking details and transparency in times of war
Re:Windows 10 0day exploit goes wild, and so do Microsoft ma...
by SlashmanX on Monday February 06, 2017 @05:42AM
(#13578276)
That's not what this article is about though really
Re:Windows 10 0day exploit goes wild, and so do Microsoft ma...
by tokenizerrr on Monday February 06, 2017 @07:12AM
(#13578720)
Sure, but the main question I had when reading the headline was if I should go into "Oh shit!" mode.
Re:Windows 10 0day exploit goes wild, and so do Microsoft ma...
by j_s on Monday February 06, 2017 @12:14PM
(#13581571)
Yes, the vulnerability is client-side AFAIK.
PoC GIF: https://twitter.com/vvalien1/status/826935182456418304
Re:Windows 10 0day exploit goes wild, and so do Microsoft ma...
by slowmotiony on Monday February 06, 2017 @06:44AM
(#13578558)
Thanks