Avoid sharing IAM roles with multiple Lambda functions. As permissions are added to the role, these are shared across all functions using this role. By using one dedicated IAM role per function, you can control permissions more intentionally.
Execute actions that should be restricted to other groups or roles.
Every Lambda function should have a 1:1 relationship with an IAM role. Even if some functions have the same policy initially, always separate the IAM roles to ensure least privilege policies.
Authenticated attacker from the Internet with access to a misconfigured role.
Expected Remediation Time
⌚ 30 minutes.
Default score using CVSS 3.1. It may change depending on the context of the src.
- Attack vector: N
- Attack complexity: H
- Privileges required: H
- User interaction: N
- Scope: U
- Confidentiality: L
- Integrity: L
- Availability: N
- Exploit code madurity: U
- Remediation level: U
- Report confidence: R
- Vector string: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N/E:U/RL:U/RC:R
- Base: 3.3
- Temporal: 2.9
- Base: Low
- Temporal: Low
- 095.Define users with privileges
- 096.Set user's required privileges
- 186.Use the principle of least privilege
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.