Timeline for Vulnerability / exploit MSDT (CVE-2022-30190) | Is renaming the registry key "ms-msdt" enough for the workaround?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 2, 2022 at 5:36 | comment | added | éclairevoyant | You don't need to backup the entire registry, you can store a reg file containing only the applicable keys if you so wish. Presumably this data would be identical across machines anyway. | |
| May 31, 2022 at 16:50 | comment | added | Ramhound | You are aware you would only have to keep a single backup of the key, right, since the keys to handle the URL handle would be identical across all your machines. With the key deleted you go from a situation where the URL handle can be used or change to not existing. Of course the real solution is to use Microsoft Defender to detect and block the malicious behavior. | |
| May 31, 2022 at 14:26 | vote | accept | marsh-wiggle | ||
| May 31, 2022 at 14:18 | comment | added | anon | The article suggests that up to date Windows Defender (WIN 10 / 11) will mitigate the threat. | |
| May 31, 2022 at 14:18 | answer | added | harrymc | timeline score: 2 | |
| May 31, 2022 at 14:14 | history | edited | marsh-wiggle | CC BY-SA 4.0 |
added 237 characters in body
|
| May 31, 2022 at 13:40 | comment | added | spikey_richie | Best to follow the Microsoft guidance on this, rather than try and come with an elaborate solution. | |
| May 31, 2022 at 13:38 | history | asked | marsh-wiggle | CC BY-SA 4.0 |