Some S3 buckets do not explicitly enable the Server-Side-Encryption (SSE) property. So the stored objects are not encrypted at rest, exposing their content to leaks by attackers or unauthorized users.
Compromise sensitive data stored in the bucket in plaintext.
Enable the SSE property in all S3 instances.
Authenticated attacker from Internet with access to the bucket.
Expected Remediation Time
⌚ 15 minutes.
Default score using CVSS 3.1. It may change depending on the context of the src.
- Attack vector: N
- Attack complexity: L
- Privileges required: L
- User interaction: N
- Scope: U
- Confidentiality: H
- Integrity: N
- Availability: N
- Exploit code madurity: P
- Remediation level: O
- Report confidence: C
- Vector string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C
- Base: 6.5
- Temporal: 5.9
- Base: Medium
- Temporal: Medium
- 134.Store passwords with salt
- 135.Passwords with random salt
- 185.Encrypt sensitive information
- 227.Display access notification
- 229.Request access credentials
- 264.Request authentication
- 300.Mask sensitive data
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.