Custom vulnerability order
Hi, I saw from the report that it searches for some useless vulnerabilities and it doesn't just waste ton of time sorting false positives but it also costs ton of tokens. For example SSRF is the biggest waste for automations, %99 of the time it's either expected functionality of the app or it's blind SSRF which is totally useless and also it's one of the bugs that requires ton of tries -> token waste, due to WAF bypass trials and also it first tries to get AWS metadata data, then sends dezons of local port disclosure requests, then tries protocols other than HTTP etc.
Also there are much better vulnerabilities that LLMs can find much more easily (like cache poisening, web cache deception, RTLO, postMessage XSS etc.). So I want to ask how can we prioritize the vulnerabilities?
Source: KeygraphHQ/shannon