[datagov-brokerpak-solr] Security Group allows open ingress/egress

[nickumia-reisys]

Date of report: 12/06/2022
Severity: Low

Due date is based on severity and described in RA-5. 15-days for Critical, 30-days for High, and 90-days for Moderate and lower.

• Security Group allows open ingress (Moderate)
  • Detailed paths
    • Path: terraform/ecs/provision/lb-leader.tf
    • Introduced through:
      • input › resource › aws_security_group[solr-lb-sg] › ingress[0]
      • input › resource › aws_security_group[solr-lb-sg] › ingress[1]
      • input › resource › aws_security_group[solr-lb-sg] › ingress[2]
  • This issue is...
    • That inbound traffic is allowed to a resource from any source instead of a restricted range
  • The impact of this is...
    • That potentially everyone can access your resource
  • You can resolve it by...
    • Set cidr_block attribute with a more restrictive IP, for example 192.16.0.0/24
• AWS Security Group allows open egress (Low)
  • Detailed paths
    • Path: terraform/ecs/provision/lb-leader.tf
    • Introduced through:
      • resource › aws_security_group[solr-lb-sg] › egress[1]
  • This issue is...
    • The inline security group rule allows open egress
  • The impact of this is...
    • Open egress can be used to exfiltrate data to unauthorized destinations, and enable access to potentially malicious resources
  • You can resolve it by...
    • Set egress.cidr_blocks attribute to specific ranges e.g. 192.168.1.0/24

[nickumia-reisys]

Superseded by

• [Snyk] Security Group allows open ingress/egress GSA-TTS/datagov-brokerpak-solr#79