Granting a user the 'lambda:CreateFunction', 'lambda:InvokeFunction', and 'iam:PassRole' permissions with the Resource set to "*" allows them to create and execute Lambda functions under any IAM role, potentially escalating their privileges in the AWS environment. This misconfiguration means the user can attach highly privileged roles to their Lambda functions and run them, effectively gaining any permissions those roles have—including full administrative access—without approval or oversight. If left unaddressed, this could lead to complete compromise of AWS resources, data theft, or account takeover.
resource"aws_iam_user""cosmic"{name="cosmic"}resource"aws_iam_user_policy""test_inline_policy"{name="test_inline_policy"user=aws_iam_user.cosmic.namepolicy= jsonencode({Version="2012-10-17"Statement=[{Action=["lambda:CreateFunction","lambda:InvokeFunction"]Effect="Allow"Resource="*"},]})}resource"aws_iam_policy_attachment""test-attach"{name="test-attachment"users=[aws_iam_user.cosmic.name]roles=[aws_iam_role.role.name]groups=[aws_iam_group.group.name]policy_arn=aws_iam_policy.policy.arn}resource"aws_iam_policy""policy"{name="test-policy"description="A test policy"policy= jsonencode({Version="2012-10-17"Statement=[{Action=["iam:PassRole",]Effect="Allow"Resource="*"},]})}
1
2
rulesets:- Terraform / AWS # Rules to enforce / AWS.
맞춤형 데모 요청
Datadog 시작하기
Ask AI
AI-generated responses may be inaccurate. Verify important info.