-
Notifications
You must be signed in to change notification settings - Fork 606
Valid JSON is blocked by Rule ID 15 #457
Comments
Hey @Punamu thanks for the issue, gonna have a quick look into it :) |
I did some tests and can confirm the issue. In the meanwhile, if you feel diving into the json parser, feel free to do so, the code is in a separate file and rather trivial |
* Setup json scanning to allow for arrays as the parent type * rather than assuming an object, just validate any json value * keep as close to the original as possible * Since all the validation comes within val we don't need to increment off. Initial tests seemed to work * Fix formatting issue
* Setup json scanning to allow for arrays as the parent type * rather than assuming an object, just validate any json value * keep as close to the original as possible * Since all the validation comes within val we don't need to increment off. Initial tests seemed to work * Fix formatting issue
Hello, I found another bug in the same file, it seems that it also cause blocking valid JSON, file was |
nice find. i will fix it! |
@phoenixstudiodz this has been fixed here: wargio/naxsi@a96f12c |
OK, great, Thank you @wargio |
Hi,
I have noticed, that the internal rule ID 15 blocks valid JSON bodies.
The following POST-bodies were tested on naxsi version 0.56 (nginx 1.10.3):
null
,true
,1337
,"some string"
,["array", "of", "strings"]
,[{"test":123},{"test":123}]
It seems that only JSON objects like
{"test":123}
are passed through.The text was updated successfully, but these errors were encountered: