-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: extra760 results in success despite errors #1014
Comments
Could you check if your role As you can see, action
|
This check has a grep for AccessDenied as below if [[ $(echo "$LIST_OF_FUNCTIONS" | grep AccessDenied) ]]; then
textInfo "$regx: Access Denied trying to list Lambda functions" "$regx" "$lambdafunction"
continue
fi But other checks has a grep with more options, like below if [[ $(echo "$SSM_DOCS" | grep -E 'AccessDenied|UnauthorizedOperation|AuthorizationError') ]]; then
textInfo "$regx: Access Denied trying to list documents" "$regx"
continue
fi
Should all grep checks for AccessDenied looks like the second one? |
This check uses
|
@lazize thank you for the pointer, I confirm the It appears that the role descriptions are not in sync. I am using |
Those files you mention has much more permissions than others. Even though they are not in sync. Keep all those files in sync is a very hard job to do it manually. I believe it will need a better mechanism to handle this situation. Just rely on people is not good enough. |
@toniblyx How about the questions above about |
Thanks @lazize we will review and merge it next week. |
What happened?
In check
extra760
, thelambda:GetFunction
returns a permission denied error, but the function returns aPASS
. See logs below (Account ID masked, but otherwise log output captured as-is).This is a follow-up to #940. The fix mentioned there only considers
lambda:ListFunction
, but not thelambda:GetFunction
, which is the actual culprit.Error message
How to reproduce it
Run prowler with check
extra760
on an environment with Control Tower.Expected behavior
A clear and concise description of what you expected to happen.
FAIL!
instead ofPASS!
, and also less noise on the output (curl errors etc.)Screenshots or Logs
If applicable, add screenshots to help explain your problem.
Also, you can add logs (anonymize them first!). Here a command that may help to share a log
bash -x ./prowler -options > debug.log 2>&1
then attach heredebug.log
From where are you running Prowler?
Please, complete the following information:
aws --version
]:./prowler -V
]: Prowler 2.7.0-24January2022Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: