Carry-on regardless
To the russian attackers, please continue and don't stop until they discontinue this pile of crap
Russia-linked attackers are already exploiting Microsoft's latest Office zero-day, with Ukraine's national cyber defense team warning that the same bug is being used to target government agencies inside the country and organizations across the EU. In an alert published on Sunday, CERT-UA says the activity is being driven by …
Why would microsoft ever discontinue such a cash cow?
Microsoft wouldn't discontinue it even if every last instance was persistently exploited (oh wait, that's the whole idea of proprietary software - the developer exploits every last user).
Interestingly the exploit doesn't seem applicable if you just used libreoffice, moreso if run on GNU/Linux.
The proper answer is diversity. This is why in biology, no virus manages to destroy all individuals of a species. To promote this, governements at least should use only open standard document formats, and these must be enforced: Like if a word processor (from whatever vendor or open-source project) messes the layout in an extensive test suite, it shall not be used. There are standards for items like paper sizes and even the properties of ball-point pen ink, so why not word processors?
Yes, there is a remote backdoor in windows 10 that allows microsoft to make whatever arbitrary changes remotely (the auto-update feature).
Although the exploit is carried out against office, a flaw in windows allows for attacker persistence - it's up to microsoft to choose whether to fix that flaw in windows 10 and choose if to roll out the patch to only "extended-support" systems or all systems.
Currently running Office 2019 on W10 (both x64 versions) on a couple of laptops.
Whilst I had update other Microsoft products in Windows Update and within Office it was set to automatically update, I had to manually (in Office) click on the update now to get it to go and fetch and install the security update “now”; I suspect if I had waited a month the automatic update scheduler would have got around to applying the update.
The mitigation offered blocked the specific malware -- it blocked use of the legacy IE engine used by the script.
It ~appears~ to me that the bug is that you can avoid a authorization step by moving between 64bit Application and 32bit com object, but I may have misunderstood that.