Description:

Memcached is an open-source, easy-to-use, high-performance, in-memory data store. It is a general-purpose distributed memory-caching system intended to speed up dynamic web applications by reducing the database load. It's used as a cache or session store. It is a popular choice for powering real-time applications in Web, Mobile Apps, Gaming, Ad-Tech, and E-Commerce.

Memcached is a Memcached-compatible in-memory key-value store service that can be used as a cache or a data store.

Security groups provide stateful filtering of ingress/egress network traffic to AWS resources. It is recommended that no security group allows unrestricted ingress access to Memcached port 11211.


Rationale:

Removing unfettered connectivity to remote console services, such as SSH, reduces a server's exposure to risk. 


Impact:

For updating an existing environment, care should be taken to ensure that administrators currently relying on an existing ingress from 0.0.0.0/0 have access to Memcached port 11211 through another security group and also prevent the cache poisoning attack.


Default Value:

VPC automatically comes with a default security group. If you don't specify a different security group when you launch the instance, the default security group will be associated with the instance. By default, the security group allows all inbound connections.  Memcached is running on the default port 11211.


Pre-Requisites

  1. Before starting, the below implementation steps write all configurations which IP and which port in the inbound.
  2. Avoid the login through the Root user.
  3. Only authorized persons (i.e, admins) can access the Security Groups.
  4. You cannot delete the default security groups but you can edit and modify them here you can create security groups and create your own rules in them.
  5. Do not attach the default security group to any EC2 instance.

Remediation:


Test Plan:

The following steps to determine if the account is configured as prescribed:

  1. log in to AWS Management Console and go to VPC https://console.aws.amazon.com/vpc/home 
  2. Go on Security Groups in the left navigation
  3. To audit select all Security group one by which contain Memcached port 11211  in the inbound
  4. Click the Inbound Rules tab
  5. Ensure no rule exists that has a port range that includes Memcached port 11211 and has a Source of 0.0.0.0/0


Using AWS CLI

The following command describes a security group the command you can use for each security groups individual to check which IP or ports inbound or outbound

aws ec2 describe-security-groups --region us-east-1 --filters \
Name=ip-permission.from-port,Values=11210 Name=ip-permission.to-port,Values=11212 \
Name=ip-permission.cidr,Values='0.0.0.0/0' \
--query 'SecurityGroups[*].{Name:GroupName}'


Implementation Steps

Perform the following steps to implement the prescribed state:

Step 1: Sign in to the AWS Management Console.

Step 2: Go to the EC2 dashboard at https://console.aws.amazon.com/ec2/.

Step 3: Click on Security Groups, under the NETWORK & SECURITY section, in the left navigation pane

Step 4: Select the appropriate security group (see Test Plan section to identify the right one(s)).

Step 5: Select the Inbound tab and click the Edit inbound rules button.


Step 6: In the Edit inbound rules dialog box, go-to source column and perform one of the following actions to restrict the inbound traffic: Click on the source dropdown

  1. Select My IP to allow inbound traffic only from your machine (i.e, from your IP address only).


Select Custom and enter IP addresses or name or ID of another security group based on your access requirements 


Step 7: Click Save to apply the changes. 


Using AWS CLI

Remove the inbound rule(s) that permits unrestricted ingress to TCP port 11211 from the selected Security Group

aws ec2 revoke-security-group-ingress --region <region> \
--group-name <group_name> --protocol tcp --port 11211 --cidr 0.0.0.0/0

Optionally add a more restrictive ingress rule to the selected Security Group

aws ec2 authorize-security-group-ingress --region <region> \
--group-name <group_name> --protocol tcp --port 11211 --cidr <cidr_block>


Backout Plan:

If you want to proceed with previous settings go through the Implementation steps section and set all previous policies that you have written somewhere.

You can delete your new security group by following steps:

  1. Open the Amazon VPC console https://console.aws.amazon.com/vpc/
  2. In the navigation pane, choose Security Groups.
    The above only for example please choose the security group which created by you do not select the default security group. and then click on Actions scroll down and click on Delete security groups we see in the below step.
  3. Select one or more security groups and choose Security Group Actions, Delete Security Group.
  4. In the Delete Security Group dialogue box, choose Yes, Delete
    or if any issue to access your port 11211 then assign the CIDR 0.0.0.0/0 in the inbound to the security group


Using AWS CLI

The following command is used to delete the created security group id in the security_group_id enter the security group id you show on your console.

aws ec2 delete-security-group --group-id <security_group_id>


Reference:

  1. AWS::EC2::SecurityGroupIngress - AWS CloudFormation

  2. revoke-security-group-ingress — AWS CLI 1.19.97 Command Reference

  3. https://aws.amazon.com/elasticache/memcached