Protocol Handler Vulnerability Fix for CVE-2018-1000006


#1

In order to mitigate this, is it enough to update to one of the versions mentioned in the blog post or do we have to additionally use the setAsDefaultProtocolClient() or append the double dashes?

We are currently registering the protocol handler in our MSI installer, like this: "MainExe" --url "%1". If I would want to use the double dashes, where would they go?

Thanks.