All Redis 3.2.x versions are affected. It’s been already four days, but it’s better late, than never.
IMPACT:
The gist is that using CONFIG SET calls (or by manipulating redis.conf) an attacker is able to compromise certain fields of the “server” global structure, including the aof filename pointer, that could be made pointing to something else. In turn the AOF name is used in different contexts such as logging, rename(2) and open(2) syscalls, leading to potential problems.
Please note that since having access to CONFIG SET also means to be able to change the AOF filename (and many other things) directly, this issue actual real world impact is quite small, so I would not panik: if you have CONFIG SET level of access, you can do more and more easily.
Well, first you have to check if you’re on 3.2.x branch. If that’s the case, then check your distro’s security announcement page for security update (e.g. for Debian Debian -- Security Information) and perform upgrade as soon possible, but it’s better to sign up for security announcement mail list or RSS feed to be up to date.
Versions 3.0 and 2.x are not vulnerable, so no need for actions to be taken.
Not sure if something has to be done via bench later.
It’s true. Probably the logic is that Debian stable (which has unaffected Redis 2.8.17) is supposed to be used on servers, but Sid and Stretch will be updated soon anyway.