Redis reachable from the internet without a password
Redis listens on 6379 and, by default, has no authentication. Bound to a public interface without a password, anyone who reaches it has full read/write access to the data and often the host.
Why it matters
Open Redis is a long-running mass-exploitation target: attackers read and wipe data, and abuse Redis features to write SSH keys or cron jobs and take the server.
It's usually exposed by binding to 0.0.0.0 plus an open firewall, with protected-mode disabled.
How to check for it
- From outside, redis-cli -h <ip> ping — a PONG without AUTH means it's open.
- Check the bind directive and that requirepass (or ACLs) is set and the port isn't open in the firewall.
How to fix it
- Bind Redis to localhost or a private interface, require a strong password (or ACL users), and keep 6379 off the public internet.
- Leave protected-mode on, and put Redis behind the application network, never facing the internet.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Is a password enough if the port is public?
- It helps, but a public data port is still brute-forceable and a bigger attack surface — keep Redis on a private network as well.