The 3388 and 3389 ports vulnerability has been around for as long as I can remember, back to Windows 95 as a concern for mainstream users. In the enterprise, they’ve always been on the security to-do list.
How many know what Remote Desktop is or even know it exists? (That’s rhetorical.) And it doesn’t exist in Windows 7 Home. I can’t recall how it’s implemented in all the vast and sundry versions of 8 and 10.
A common practice for the port 3388/3389 thing has been to find Remote Desktop Configuration and Remote Desktop Services in services.msc and set them to disable if not already in that state.
While you’re at it, right click on Computer, select Properties, click on Remote Settings and uncheck “Allow Remote Assistance…” if not already in that state.
Those running with and savvy with Windows Firewall can create rules to block ports 3388 & 3389, too.
Unless I’m mistaken, properly configured, GlassWire should alert with a first network connection if an outbound session is initiated.
Which is not to say you shouldn’t run Windows Update. The current fix will be OK until the next 3388/3389 hack is whipped up.
Anyhow, as the Ars Technica article reports, “Much of the attack traffic we see against RDP appears to be directed specifically at point-of-sale systems…” These will be fixed once the retailers happen to note all the customers lined up at the cash registers.