Common attacks and weaknesses
- Unauthenticated access to all data.
- CONFIG SET abused to write SSH keys or cron jobs and take over the server.
- Cryptominer campaigns targeting exposed instances.
Redis in-memory data store. Historically shipped without authentication.
The application reads and writes values kept in memory: answers come back in well under a millisecond. Encryption is optional: traffic is only protected if TLS is enabled on the server and the client.
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| redis | 6379 | TCP | An advanced key-value cache and store | - | 2015-04-23 |
| - | 6379 | - | Reserved | - | - |
// source: IANA service name and port number registry
Linux
sudo ss -ltnup 'sport = :6379' # process listening on 6379
sudo lsof -nP -i :6379macOS
sudo lsof -nP -i :6379
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 6379 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 6379 netstat -ano | findstr :6379
From another machine
nmap -p 6379 -sV <host> nc -zv <host> 6379
Block it in the firewall
sudo ufw deny 6379/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 6379" -Direction Inbound -LocalPort 6379 -Protocol TCP -Action Block # Windows
Redis in-memory data store. Historically shipped without authentication.
Port 6379 is registered for TCP.
It is rated 9/10 (critical) when exposed to the Internet. Unauthenticated access to all data. Bind to localhost and keep protected-mode on.
On Linux run "ss -ltnup 'sport = :6379'", on macOS "lsof -nP -i :6379", and on Windows "netstat -ano | findstr :6379" to see the local process. From another machine, "nmap -p 6379 <host>" shows whether it is reachable.