That is very very late. This type of error was inexcusable back in 2009 when Redis first came about. There is no reason to trust this product.
Re:Securing a Postgres Database
by diamond_hands on Friday April 02, 2021 @09:26PM
(#26677656)
3.2.0 came out 5 years ago. I think it's okay now.
Not anymore since version 3.2.0 [0]
>Unfortunately many users fail to protect Redis instances from being accessed from external networks. Many instances are simply left exposed on the internet with public IPs. For this reasons since version 3.2.0, when Redis is executed with the default configuration (binding all the interfaces) and without any password in order to access it, it enters a special mode called protected mode. In this mode Redis only replies to queries from the loopback interfaces, and reply to other clients connecting from other addresses with an error, explaining what is happening and how to configure Redis properly.
[0] https://redis.io/topics/security