-
-
Notifications
You must be signed in to change notification settings - Fork 705
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
alessiodallapiazza
wants to merge
8
commits into
zaproxy:main
Choose a base branch
from
alessiodallapiazza:fix-false-positive-cloud-metadata
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
ascanrules: fix false positive in cloud metadata #5729
alessiodallapiazza
wants to merge
8
commits into
zaproxy:main
from
alessiodallapiazza:fix-false-positive-cloud-metadata
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
zapbot
added a commit
to zaproxy/cla
that referenced
this pull request
Sep 17, 2024
thc202
changed the title
Fix false positive cloud metadata
ascanrules: fix false positive imcloud metadata
Sep 17, 2024
thc202
changed the title
ascanrules: fix false positive imcloud metadata
ascanrules: fix false positive in cloud metadata
Sep 17, 2024
Changelog should be updated and tests added. |
thc202
reviewed
Sep 17, 2024
addOns/ascanrules/src/main/java/org/zaproxy/zap/extension/ascanrules/CloudMetadataScanRule.java
Outdated
Show resolved
Hide resolved
kingthorin
reviewed
Sep 17, 2024
addOns/ascanrules/src/main/java/org/zaproxy/zap/extension/ascanrules/CloudMetadataScanRule.java
Outdated
Show resolved
Hide resolved
thc202
reviewed
Sep 17, 2024
addOns/ascanrules/src/main/java/org/zaproxy/zap/extension/ascanrules/CloudMetadataScanRule.java
Outdated
Show resolved
Hide resolved
addOns/ascanrules/src/main/java/org/zaproxy/zap/extension/ascanrules/CloudMetadataScanRule.java
Outdated
Show resolved
Hide resolved
addOns/ascanrules/src/main/java/org/zaproxy/zap/extension/ascanrules/CloudMetadataScanRule.java
Outdated
Show resolved
Hide resolved
kingthorin
reviewed
Sep 17, 2024
addOns/ascanrules/src/main/java/org/zaproxy/zap/extension/ascanrules/CloudMetadataScanRule.java
Outdated
Show resolved
Hide resolved
kingthorin
approved these changes
Sep 17, 2024
There was a problem hiding this 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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