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

Add an 'indication' element #3

Open
psiinon opened this issue Jun 5, 2013 · 3 comments
Open

Add an 'indication' element #3

psiinon opened this issue Jun 5, 2013 · 3 comments

Comments

@psiinon
Copy link
Member

psiinon commented Jun 5, 2013

Another optional one, but one that tools can use to indicate the string that they identified which indicates the problem.
This can help the user sanity check the vulnerability.

@dancornell
Copy link
Member

Would this be like the payload that was used to exploit a dynamic vulnerability?

@psiinon
Copy link
Member Author

psiinon commented Jun 6, 2013

No, although thats useful to include as well :)
So the payload could be: <script>alert(1);</script>
while the indication (ie whats in the resulting page) would probably be: <script>alert(1);</script>

I use that in ZAP to highlight the relevant part of the response - a user can then look at that and hopefully more easily make a better judgement as to whether its a false positive or not.

@psiinon
Copy link
Member Author

psiinon commented Jun 6, 2013

Typical - github translated my payloads and indications!
So the payload was an encoded version of the std basic script attack.
Lets try again...
Payload:

&#x3C;&#x73;&#x63;&#x72;&#x69;&#x70;&#x74;&#x3E;&#x61;&#x6C;&#x65;&#x72;&#x74;&#x28;&#x31;&#x29;&#x3B;&#x3C;&#x2F;&#x73;&#x63;&#x72;&#x69;&#x70;&#x74;&#x3E;

Indication:

 <script>alert(1);</script>

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

No branches or pull requests

2 participants