Closed blindpet closed 8 years ago
The rule triggered does not make any sense for this text. Can you explain what symbols it does not like? Perhaps you could capture the POST body in your web browser so we could see how it looks on the wire?
Furthermore, does commenting out sql.vcl rule 11 work around this false positive?
Regards.
Will see if I can do the capture tomorrow.
Disabling rule 11 in sql.encoded does make the problem go away so that's what I've done for now.
ah, it's sql.encoded, that makes more sense, it's "update" followed by "set". I'm marking the whole ruleset for revamping..
On Mon, Nov 30, 2015 at 1:20 AM, blindpet notifications@github.com wrote:
Will see if I can do the capture tomorrow.
Disabling rule 11 in sql.encoded does make the problem go away so that's what I've done for now.
— Reply to this email directly or view it on GitHub https://github.com/comotion/VSF/issues/30#issuecomment-160485921.
http://comotion.delta9.pl http://u.delta9.pl http://kacper.doesntexist.org Too much order is its own chaos. Employ no technique to gain supreme enlightment.
That's another thing while you're at it, the marks for debugging for sql and sql.encoded are the same i believe (at least I looked in sql.rules first based on the logs)
That I can do something with, see commit f7dfed1073c2d4bb5015392a2e50b752af926de3.
False positives are bound to happen with rules like this, the procedure is to identify and disable rules that do not fit the application well. Thanks for reporting!
Installed this to protect mybb and getting a false positive for an sql injection when sending a message with this text
Varnishlog
Upon further testing it appears to not like the symbols in this text