Added Profile header for additional WAP coverage on CJServer hosts #6337
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
|
Hello @pect0ral, thank you so much for sharing this template with the community and contributing to this project 🍻 |
DhiyaneshGeek
approved these changes
Dec 12, 2022
princechaddha
added
the
Status: Completed
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.
Template / PR Information
Added the Profile HTTP header after finding this also susceptible on certain CJServer instances. May AID in still getting OOB when WAF is filtering X-WAP-Profile. Confirmed working.
Tested against known vulnerable host
Template Validation
I've validated this template locally?
Additional Details (leave it blank if not applicable)
Additional References: