Fix IIS Internal IP Disclosure #4479
Merged
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
Fix IIS Internal IP Disclosure for OWA case
ehsandeep
approved these changes
May 25, 2022
There was a problem hiding this comment.
Thanks for the heads up and update @y0no, we can actually keep both one with stop-at-first-match, I also updated the matcher to filter out some false positive results which matches against other parts of header response, now it will only look to match with location header.
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.
In some cases, the IIS Internal IP Disclosure template does not works. The "Host" header need to be completly removed to avoid getting a 400 Bad Request (Invalid Host Header) error. In addition, the status code used to check the vulnerability can be 302 or 301.
Template Validation
I've validated this template locally?