Unrestricted mysql access remediation

Using Console

To remediate the unrestricted MySQL access issue in AWS, you can follow the below steps:

Login to AWS console.
Go to the RDS service.
Select the DB instance with unrestricted MySQL access.
Click on the “Modify” button.
Scroll down to the “Network & Security” section.
In the “Security Group” section, select the security group associated with the DB instance.
Click on the “Remove” button to remove the inbound rule that allows unrestricted access to MySQL.
Add a new inbound rule to the security group that allows access only from specific IP addresses or CIDR blocks.
Click on the “Save Changes” button to apply the changes.

By following the above steps, you can remediate the unrestricted MySQL access issue in AWS and ensure that your database is secure.

Using CLI

To remediate the unrestricted MySQL access issue in AWS using AWS CLI, follow the below steps:Step 1: Open the AWS CLI and run the following command to list all the security groups in your AWS account:

aws ec2 describe-security-groups

Step 2: Identify the security group that has unrestricted MySQL access. You can filter the results using the following command:

aws ec2 describe-security-groups --filters Name=ip-permission.protocol,Values=tcp Name=ip-permission.to-port,Values=3306 Name=ip-permission.cidr,Values='0.0.0.0/0'

This command will list all the security groups that have unrestricted MySQL access.Step 3: Once you have identified the security group, run the following command to revoke the MySQL access:

aws ec2 revoke-security-group-ingress --group-id <security-group-id> --protocol tcp --port 3306 --cidr 0.0.0.0/0

Replace <security-group-id> with the ID of the security group that you want to remediate.Step 4: Verify that the MySQL access has been revoked by running the following command:

aws ec2 describe-security-groups --group-ids <security-group-id>

This command will list the details of the security group that you have remediated.That’s it. You have successfully remediated the unrestricted MySQL access issue in AWS using AWS CLI.

Using Python

To remediate unrestricted MySQL access in AWS using Python, you can follow these steps:

Import the necessary libraries:

import boto3
from botocore.exceptions import ClientError

Create an AWS client for the RDS service:

rds = boto3.client('rds')

Get a list of all RDS instances:

try:
    response = rds.describe_db_instances()
    instances = response['DBInstances']
except ClientError as e:
    print(e)
    exit(1)

Loop through each RDS instance and modify its security group to remove unrestricted MySQL access:

for instance in instances:
    db_instance_identifier = instance['DBInstanceIdentifier']
    db_security_groups = instance['DBSecurityGroups']
    for security_group in db_security_groups:
        if security_group['DBSecurityGroupName'] == 'default':
            try:
                response = rds.revoke_db_security_group_ingress(
                    DBSecurityGroupName='default',
                    EC2SecurityGroupId=security_group['EC2SecurityGroups'][0]['EC2SecurityGroupId'],
                    CIDRIP='0.0.0.0/0',
                    DBProtocol='tcp',
                    DBPortNumber=3306
                )
                print(f"Revoked unrestricted MySQL access for {db_instance_identifier}")
            except ClientError as e:
                print(e)
                exit(1)

This code will loop through each RDS instance and its associated security groups. If the default security group is found, it will revoke any inbound rules that allow unrestricted MySQL access (i.e. from any IP address). The code will print a message for each instance where unrestricted MySQL access was revoked.

Using Terraform

# Security group without any 0.0.0.0/0 or ::/0 ingress on port 3306
resource "aws_security_group" "mysql_sg" {
  name        = "mysql-sg"
  description = "MySQL security group without unrestricted access"
  vpc_id      = AWS_VPC_ID   # replace with your VPC ID
}

# Example of a more restrictive IPv4 rule (optional replacement):
# allow MySQL only from a trusted CIDR
resource "aws_vpc_security_group_ingress_rule" "mysql_from_trusted_ipv4" {
  security_group_id = aws_security_group.mysql_sg.id

  cidr_ipv4   = "TRUSTED_IPV4_CIDR"  # e.g. "203.0.113.0/24"
  from_port   = 3306
  to_port     = 3306
  ip_protocol = "tcp"
}

# Example of a more restrictive IPv6 rule (optional replacement):
# allow MySQL only from a trusted IPv6 prefix
resource "aws_vpc_security_group_ingress_rule" "mysql_from_trusted_ipv6" {
  security_group_id = aws_security_group.mysql_sg.id

  cidr_ipv6   = "TRUSTED_IPV6_CIDR"  # e.g. "2001:db8:1234::/64"
  from_port   = 3306
  to_port     = 3306
  ip_protocol = "tcp"
}

To match the CLI remediation, delete (or edit) any existing aws_vpc_security_group_ingress_rule resources that currently have:

cidr_ipv4 = "0.0.0.0/0" and from_port = 3306, to_port = 3306, ip_protocol = "tcp", and/or
cidr_ipv6 = "::/0" and from_port = 3306, to_port = 3306, ip_protocol = "tcp".

WARNING: Removing these rules will cut off existing MySQL access from the internet and may cause a service outage if anything depends on it.terraform plan should show the offending aws_vpc_security_group_ingress_rule resources with cidr_ipv4 = "0.0.0.0/0" and/or cidr_ipv6 = "::/0" on port 3306 being destroyed (or modified to the new, restricted CIDRs).

AWS Introduction

AWS Pricing

AWS Threats

AWS Misconfigurations

Unrestricted mysql access remediation

Triage and Remediation

Remediation

​Triage and Remediation

​Remediation

​

Triage and Remediation

Remediation