Not Microsoft at least. Most vendors, and the percentage grows with the size of the vendor, are very coy about it. And I get it: it doesn't look great for your shareholders, and it gets to a point where yes really you should be ashamed (looking at HP Data Protector here (note the irony)), but if you own it up and also put countermeasures and hardening in place then really everyone is going to feel like they got their money's worth in the end. If instead you hide vulnerabilities, not mention them in changelogs so we can't even check which version is fixed or anything, yeah we'll be recommending the client to look at alternatives. (Though it's not us security consultants that ever recommended a sysadmin to put a proprietary VPN in place in the first place, but then there's more at play than purely the security aspect.)
Microsoft's advantage, of course: try getting out of that ecosystem if you have everyone implicitly trained in using Outlook and Windows. Microsoft gets to do with their advisories whatever the hell they like.
So it's more like victims not updating their software.
But yes, of course the #1 recommendation is for our clients to Always Install Patches Immediately. Always. And they never ever do it. For comparison, though, OpenSSH needed to be updated for a critical vulnerability last in... 2002, maybe? Secure protocols can be done, so it's not only the people not installing updates that are to blame here.
Exploitation unlikely at the time of exploit discovery.
A patch has been released.
This means, the reason why it shows up on the list is because people are running unpatched software. And it's really alarming because the 2017 CVE is for Office 2007 that's ~15 years old (with a patch available!).
Replying to your edit:
> that's ~15 years old (with a patch available!)
I haven't looked into this one, but you mention it's a 2017 CVE. That means the vuln was discovered (not even necessarily patched and disclosed) in 2017 and not 15 years ago. The age of the product isn't the same as how fast they install security updates (but yeah apparently 2-3 years depending on the exact timeline (the stats are from 2020), so that's practically never).
Sure, but it's a CVE for a 15 year old software. At this point, running 15 year old software unpatched on machines connected to internet is just negligence on user's part. Maybe we do need forced updates as default.
Anecdote: latest set of windows patches did something to Bluetooth, such that when I switch my mouse between machines there's up to a 3 second lag before the cursor is responsive. Big deal, minor nuisance, right? Except if I'm in a Fullscreen application, it causes a blue screen because the os waiting for the mouse to handshake pauses the GPU for some reason, and the GPU-Windows framework panics and blue screens to prevent hardware damage. This has the side effect of corrupting the application that was running during the blue screen, sometimes forcing a reinstall.
I have no idea what patch it was that caused this, nor can I really expect anyone to fix it, how often are most(98%?) users connecting and disconnecting their mouse every day? I'm switching it dozens of times an hour.
Since Vista GPU hangs or TDRs don't cause blue screen. It's likely something else that's causing your system to hangup on bluetooth connections. Your best bet is to file a feedback hub bug, if enough people are facing it - our tools will flag either the update or the device drivers identified as common in crash dumps.
If you're keen, I could take a look at your crash dump file. My email is firstname.lastname@microsoft.com (you'll find me at github.com/zeusk)