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

Multi-path discovery function #221

Open
killpi opened this issue Jul 29, 2024 · 1 comment
Open

Multi-path discovery function #221

killpi opened this issue Jul 29, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@killpi
Copy link

killpi commented Jul 29, 2024

What is the problem you are trying to solve?

I hope to be able to scan different levels of routing

How are you currently being hindered by this problem?

For example, some components related to Springboot may not exist in the root directory or the last level of the route due to microservices or other reasons.
Like http://example.com/code/api/gen, I want to check the env endpoint, hoping to check
/code/api/gen/env
/code/api/env
/code/env
/env,
but I refer to the manual and some current templates, it seems that this operation cannot be achieved

How would you like this problem to be solved?

Hopefully a method can be provided to obtain routes at different levels

Any additional details?

no

@killpi killpi added the enhancement New feature or request label Jul 29, 2024
@Michelle-PortSwigger
Copy link
Contributor

Hi

You could use an insertion-point-level BCheck, this would allow you to insert details into the different path/folder levels but if used with the default scan audit configuration this would also insert the payload into all other insertion point types as the BCheck itself does not give that level of granularity.

If you used the insertion-point-level BCheck, you do have the option to customise the scan audit configuration 'Insertion Point Types' to control the locations into which Scanner will place payloads.

I hope this helps to explain things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants