nemesida-waf/waf-bypass

Code exception

Closed this issue · 6 comments

Hi,it was used normally a few days ago, but now it reports an error when it is used。
Error message :
error occurred while processing payload from file path\xxx.json: list index out of range�

Hello, I don't get this error, what parameters you run to reproduce error

On my windows OS:
image

Ok, thank u, I've made fixes, try to check it now from the main branch

Might be related, but I'm getting this on my Windows box (python version is 3.11.0):

PS C:\Tools\Recon\waf-bypass> python .\main.py --host='https://<foobar>' --proxy='http://127.0.0.1:8081' --details

##
# Target:       https://<foobar>
# Proxy:        http://127.0.0.1:8081
# Timeout:      30s
# Threads:      5
# Block code:   403
# Exclude dirs:
# User-Agent:   Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36
##

�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\API\1.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\LFI\4.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\API\2.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\NoSQLi\2.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\RCE\13.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\API\3.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\LFI\5.json in URL: 0�[0m

Yes, new versions of my windows and kali both have this result, but it does not affect the generation of the result, I think it is possible that the return state of the website as long as it is not specified in the code several states will throw this exception.

Might be related, but I'm getting this on my Windows box (python version is 3.11.0):

PS C:\Tools\Recon\waf-bypass> python .\main.py --host='https://<foobar>' --proxy='http://127.0.0.1:8081' --details

##
# Target:       https://<foobar>
# Proxy:        http://127.0.0.1:8081
# Timeout:      30s
# Threads:      5
# Block code:   403
# Exclude dirs:
# User-Agent:   Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36
##

�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\API\1.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\LFI\4.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\API\2.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\NoSQLi\2.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\RCE\13.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\API\3.json in URL: 0�[0m
�[33mAn incorrect response was received while processing request from file C:\Tools\Recon\waf-bypass\payload\LFI\5.json in URL: 0�[0m

This happens when an invalid response code is received from the webserver/waf (eg 0, 100, 499, etc.). In this case, you need to fix your webserver/waf/webapp according to your last comment.