Check your Amazon EC2 security groups for inbound rules that allow unrestricted access (i.e. 0.0.0.0/0 or ::/0) on TCP port 6379 in order to reduce the exposure to security risks and protect the Redis cache server instances associated with your security groups. Redis is an open source, in-memory data structure store, used as a database, cache server, and message broker.
This rule can help you work with the AWS Well-Architected Framework
This rule resolution is part of the Cloud Conformity Security & Compliance tool for AWS
Allowing unrestricted inbound/ingress access on TCP port 6379 (Redis) to your Amazon EC2 instances can increase opportunities for malicious activities such as cross-site scripting, remote code executions, brute-force and cryptojacking attacks (e.g. RedisWannaMine attacks). The associated security groups should be configured so that the communication to specific resources is restricted to only those hosts or networks that have a legitimate requirement for access.
Audit
To determine if your Amazon EC2 security groups allow unrestricted Redis access, perform the following operations:
Remediation / Resolution
To update your Amazon EC2 security groups configuration in order to restrict Redis access to trusted entities only (i.e. authorized IP addresses and IP ranges, or other security groups), perform the following operations:
References
- AWS Documentation
- Amazon EC2 security groups for Linux instances
- Working with security groups
- Security group rules reference
- Authorizing inbound traffic for your Linux instances
- AWS Command Line Interface (CLI) Documentation
- ec2
- describe-security-groups
- revoke-security-group-ingress
- authorize-security-group-ingress
- Redis Documentation
- Redis
Unlock the Remediation Steps
Gain free unlimited access
to our full Knowledge Base
Over 750 rules & best practices
for and
Get started for FREE
You are auditing:
Check for Unrestricted Redis Access
Risk level: Very High