-
-
Notifications
You must be signed in to change notification settings - Fork 438
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
(Closed #175) Adjust XSS injection phase for targets that reflected a…
…ll injections
- Loading branch information
Showing
1 changed file
with
42 additions
and
34 deletions.
There are no files selected for viewing
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
a4bbf19
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.
Hi @hahwul , maybe I misunderstand something from just reviewing the code, but worth asking anyway.
In the new way, if this imaginary param is reflected, then you are completely skipping the mining. Is that correct? If so, you will miss cases where mining can find another param which is reflected somewhere else in the DOM.
I hope that I missed something here..
a4bbf19
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.
Hello again @rotemreiss
Yes, you're right. Virtual parameters have been reflected, but mining is required. However, there are so many unnecessary scans right now, so I applied them to filter out with the code.
The process of filtering meaningful and meaningless reflections with random parameters reflected will be included in the code section below, and logic will need to be considered more think. (Param / reflected corresponds to N*N, so I don't know if it's easy to implement.)
a4bbf19
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.
So maybe we need to allow an
aggressive
flag for such cases to continue mining anyway, or/and throw a message that the mining was skipped due to a global reflection.BTW in case of such a message, we can also provide the line number, and allow the user to set something like
skip-reflection-line=X
, and then for a narrow scope, the user will be able to initiate another scan with skipping reflections on a specific line . WDYT?