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

ascanrules: fix false positive in cloud metadata #5729

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

alessiodallapiazza
Copy link

@alessiodallapiazza alessiodallapiazza commented Sep 17, 2024

Overview

This pull request fixes the issue of false positives in the CloudMetadataScanRule plugin. The condition for raising an alert has been improved by adding a method to specifically check for both "ami-id" and "ami-launch-index" in the response body.

Fixes zaproxy/zaproxy#8514

Copy link

github-actions bot commented Sep 17, 2024

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@alessiodallapiazza
Copy link
Author

I have read the CLA Document and I hereby sign the CLA

@zaproxy zaproxy deleted a comment from alessiodallapiazza Sep 17, 2024
zapbot added a commit to zaproxy/cla that referenced this pull request Sep 17, 2024
@thc202 thc202 changed the title Fix false positive cloud metadata ascanrules: fix false positive imcloud metadata Sep 17, 2024
@thc202 thc202 changed the title ascanrules: fix false positive imcloud metadata ascanrules: fix false positive in cloud metadata Sep 17, 2024
@thc202
Copy link
Member

thc202 commented Sep 17, 2024

Changelog should be updated and tests added.

Copy link
Member

@kingthorin kingthorin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

False Positive with cloud metadata due to receiving a successful response HTTP/1.1 200 OK
3 participants