Homepage

VPC security group rule permits ingress from '0.0.0.0/0' to port 2379 (etcd) Affecting VPC service in AWS

Severity

0.0
medium
0
10
Severity Framework
Snyk CCSS
Rule category
Network/ Ports

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
CIS-ControlsCSA-CCMISO-27001NIST-800-53PCI-DSSSOC-2
  • Snyk IDSNYK-CC-00106
  • creditSnyk Research Team
Report a new misconfiguration Found a mistake?

Description

Removing unfettered connectivity to an etcd server reduces the chance of exposing critical data.

How to fix?

Set the ingress.cidr_blocks attribute with a more restrictive CIDR block, for example 192.16.0.0/24.

Example configuration:

resource "aws_security_group" "allow_some_cidr_valid" {
  name        = "allow_some_cidr_valid"
  description = "Allow from valid CIDR"

  ingress {
    from_port   = 2379
    to_port     = 2379
    protocol    = "tcp"
    cidr_blocks = ["192.16.0.0/24"]
  }
}