Insecure service configuration - Security Groups
EC2 Security Groups are not explicitly defined. Security Group input/output rules are not defined.
- Extract information from the server without proper consent.
- Create holes to gain remote access.
Securely configure the vulnerable service by explicitly defining the Security Groups.
Anonymous attacker with access to an EC2 instance from an internal network.
Expected Remediation Time
⌚ 30 minutes.
Default score using CVSS 3.1. It may change depending on the context of the vulnerability.
- Attack vector: A
- Attack complexity: H
- Privileges required: N
- User interaction: N
- Scope: U
- Confidentiality: L
- Integrity: L
- Availability: N
- Exploit code madurity: P
- Remediation level: O
- Report confidence: C
- Vector string: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C
- Base: 4.2
- Temporal: 3.8
- Base: Medium
- Temporal: Low
The services have specific security groups configured
Non compliant code
There are services with the default security groups configured
Using the AWS CLI, the following command checks if the EC2 instance uses the default security groups
$ aws ec2 describe-instances
If the output returns one or more instance ID, these have the default security group configured
Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.