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

Selecting irrelevant part in scan results #10

Open
irsdl opened this issue May 24, 2017 · 9 comments
Open

Selecting irrelevant part in scan results #10

irsdl opened this issue May 24, 2017 · 9 comments

Comments

@irsdl
Copy link

irsdl commented May 24, 2017

when an issue is found using the automated scanner and this extension, it selects (highlight) an irrelevant part of the request rather than the actual input.

image

@albinowax
Copy link
Collaborator

What kind of issue is this?

@irsdl
Copy link
Author

irsdl commented May 31, 2017

There are multiple. For example just now in my new test I have it trying to Fuzz the end of the URL but has selected something in the URLbefore the payload - perhaps it cannot predict the length after the new payload is added?

image

@albinowax
Copy link
Collaborator

It's meant to highlight the random string it injects just before the actual payload. The odd thing is it works for me fine in testing. With that latest screenshot, are you using manual insertion points specified using the intruder?

@albinowax
Copy link
Collaborator

Judging by that last screenshot, you're probably not using the latest release of backslash powered scanner. Can you try updating and see if the issue still exists?

@irsdl
Copy link
Author

irsdl commented May 31, 2017

I removed my comment - my Backslash powered scanner was outdated - will let you know how it goes on my next tests...

@albinowax
Copy link
Collaborator

Closing this, feel free to reopen if you notice the issue in the latest version.

@irsdl
Copy link
Author

irsdl commented Jun 2, 2017 via email

@irsdl
Copy link
Author

irsdl commented Jun 20, 2017

I can still recreate the issue using the latest version. It has selected this as "Magic value: null" while it had to selected the "undefined" bit - it is exactly the same in the other requests as well:

image

@SamJoan
Copy link

SamJoan commented May 9, 2018

I can verify this still occurs on the latest version obtained from the BApp store.

bugrep

Not a big issue for me though

@albinowax albinowax reopened this May 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants