Skip to content
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

Prowler Shows Confused Deputy High-Severity Fail in EU-West-1 After Fixing in US-East-1 & US-East-2 #6474

Open
Krish3600 opened this issue Jan 13, 2025 · 4 comments
Assignees
Labels
bug status/needs-triage Issue pending triage

Comments

@Krish3600
Copy link

Steps to Reproduce

Configure IAM and CloudFormation resources in us-east-1 and us-east-2 to prevent confused deputy attacks (verified via trust policies and recommended AWS configurations).
Run a Prowler scan across all regions.
Observe that Prowler flags eu-west-1 resources as “FAIL” for cross-service confused deputy checks, despite identical (or global) configurations across regions.

Expected behavior

Prowler should correctly identify that the confused deputy vulnerability has been addressed across all regions, including eu-west-1.
The checks should show a “PASS” if the policies and roles adhere to AWS best practices.
As there is no resource in eu-west-1 region

Actual Result with Screenshots or Logs

Actual Behavior (Screenshot):

Below is a screenshot demonstrating the repeated High FAIL findings in eu-west-1 for both CloudFormation and IAM (indicating a “confused deputy” vulnerability):

How did you install Prowler?

Cloning the repository from github.com (git clone)

Environment Resource

ec2-instance

OS used

Amazon linux

Prowler version

latest

Pip version

latest

Context

We have verified that all trust policies and resource configurations align with AWS recommended best practices.
Re-scanning multiple times still produces the same results.
This appears to be a false-positive or region-detection issue within Prowler.
Request:

Investigate why eu-west-1 is still showing as “FAIL” for confused deputy checks after successful fixes in other regions.
Provide any guidance or confirm if this is a bug in the scanning logic for global resources.

Please advise if there’s a configuration tweak or an updated check we can apply to resolve this discrepancy. Thank you for your help!

@Krish3600 Krish3600 added bug status/needs-triage Issue pending triage labels Jan 13, 2025
@MrCloudSec
Copy link
Member

Hi @Krish3600, thanks for reaching us out.
Can you share the trust policy the Prowler is triggering as FAIL?

@MrCloudSec MrCloudSec self-assigned this Jan 13, 2025
@Krish3600
Copy link
Author

Krish3600 commented Jan 14, 2025 via email

@MrCloudSec
Copy link
Member

Hi @Krish3600, I cannot see the screenshot, can you send it again?

@Krish3600
Copy link
Author

Krish3600 commented Jan 14, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug status/needs-triage Issue pending triage
Projects
None yet
Development

No branches or pull requests

2 participants