

I followed the instructions from Amazon and all is running well. It listens on the port specified in its configuration file, encrypts the communitation with the client, and forwards the data to the original daemon listening on its usual port. Find: Change to one to enable stunnel automatic startup ENABLED0. Once apt-get has finished we will need to enable stunnel by editing the /etc/default/stunnel4 configuration file.
AWS STUNNEL UPDATE
Update the affected package aws-efs-utils.11048 to the latest version. I signed up for Amazon SES with a Drupal 7 turnkey linux instance. The stunnel program is an encryption wrapper between a client and a server. Just like TinyProxy, the installation of stunnel is as easy as executing the apt-get command.

As a result, concurrent mount operations can allocate the same local port, leading toĮither failed mount operations or an inappropriate mapping from an EFSĬustomer’s local mount points to that customer’s EFS file systems. The mount helper allocates a local port for stunnel to receive NFSĬonnections prior to applying the TLS tunnel. The vulnerability exists due to a race condition within the Amazon EFS mount helper when using TLS to mount file systems. The stunnel config seems fine, and the /etc/stunnel/nf is not needed. The vulnerability allows a local user to perform a denial of service (DoS) attack. The Stunnel program is designed to work as an SSL encryption wrapper between remote client and local (inetd-startable) or remote server. CWE-ID: CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
