RDS DB cluster parameter group configured with TLS Version below 1.2 Affecting RDS service in AWS


Severity

0.0
medium
0
10
Severity Framework
Snyk CCSS
Rule category
Data/ Encryption in Transit

Is your environment affected by this misconfiguration?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
Frameworks
  • Snyk IDSNYK-CC-00765
  • creditSnyk Research Team

Description

Enforcing a TLS version below 1.2 for RDS DB cluster parameter groups can expose data in transit to interception or compromise due to known vulnerabilities in older TLS versions. It is essential to use TLS 1.2 or higher to ensure secure encryption standards are met and to comply with industry best practices for data protection.

How to fix?

Setrequire_secure_transport , rds.force_ssl to ON and 1 respectively and tls_version, ssl_min_protocol_version and ssl_max_protocol_version to TLSv1.2 or higher in aws_rds_cluster_parameter_group.

Example configuration:


resource "aws_rds_cluster_parameter_group" "allow1" {
  name        = "cluster-parameter-765"
  family      = "aurora-mysql5.7" 
  description = "Example DB parameter group for TLS settings"

  parameter {
    name  = "require_secure_transport"
    value = "ON"
    apply_method = "pending-reboot"
  }
  parameter {
    name  = "tls_version"
    value = "TLSv1.2"
    apply_method = "pending-reboot"
  } 
}

resource "aws_rds_cluster_parameter_group" "allow2" {
  name        = "example-parameter-group"
  family      = "aurora-postgresql15" 
  description = "Example DB parameter group for TLS settings"

  parameter {
    name  = "rds.force_ssl"
    value = "1"
    apply_method = "pending-reboot"
  }
  parameter {
    name  = "ssl_min_protocol_version"
    value = "TLSv1.2"
    apply_method = "pending-reboot"
  } 
   parameter {
    name  = "ssl_max_protocol_version"
    value = "TLSv1.3"
    apply_method = "pending-reboot"
  } 
}