Bump binaries submodule

A user reported the following:

I noticed that when Mullvad for Windows starts OpenVPN, an attempt is made to read the file
C:\etc\ssl\openssl.cnf. On most systems this file isn't present. By default Windows allows
any authenticated users to create new files in the system roots, meaning that a user can
created a directory structure C:\etc\ssl\ containing a file openssl.cnf.
When present the file will be read and processed by the OpenSSL library (OpenVPN).

A local attacker can abuse this situation by creating a configuration file containing
a malicious engine entry pointing to an attacker-controlled DLL. When the configuration
is processed, an attempt is made to load this DLL by the OpenVPN binary.
Since OpenVPN is running as LocalSystem, it is possible for any authenticated user to
run arbitrary code as LocalSystem.

Adding the no-autoload-config to the OpenSSL build options disable loading this file
on initialization. So I added this and re-built OpenVPN on all platforms.

0 files changed, 0 insertions, 0 deletions