10000 Scanning Locations Not Specified · Issue #17 · nccgroup/freddy · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Scanning Locations Not Specified #17

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

Open
Himself132 opened this issue Jul 13, 2020 · 0 comments
Open

Scanning Locations Not Specified #17

Himself132 opened this issue Jul 13, 2020 · 0 comments

Comments

@Himself132
Copy link

The extension, as ran on Kali fully up to date (7/12/2020) and Burp fully up to date (2020.6) when sending a request to Intruder and manually specifying locations to run autoscans on is injecting payloads into locations not specified.

To reproduce simply send a content-type application/json message with several parameter and value pairs and specify the locations and right click and sent to an auto-scan that is running or create a new one to send it to.

Observe requests being sent in the session tracer or by passing to another upstream proxy.

This is not desired behavior because it wastes time, and it could have potentially detrimental affects to the environment under test.

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

1 participant
0