Skip to content
This repository has been archived by the owner on Nov 8, 2023. It is now read-only.

error log field "cscore" lost when blocking "$EVADE" attack #369

Closed
lsqworld opened this issue Mar 27, 2017 · 4 comments
Closed

error log field "cscore" lost when blocking "$EVADE" attack #369

lsqworld opened this issue Mar 27, 2017 · 4 comments

Comments

@lsqworld
Copy link

Version: 0.55.1

When I made a "$EVADE" attack , I could not find the "cscore" field in it's blocked log line.

What request I've made:
http://10.110.20.19/?a=%U
And the blocked log:
qq 20170327162435

And the following is a normal "$SQL" attack block log:
qq 20170327162724

So is it just a bug or I made some error?
Thank you very much!

@lsqworld lsqworld changed the title error log field "cscore" lost when block "$EVADE" attack error log field "cscore" lost when blocking "$EVADE" attack Mar 27, 2017
@buixor
Copy link
Contributor

buixor commented Apr 6, 2017

Hello,

It is because you triggered an internal rule. Those do not set a specific named score, but just set the block flag in the request.

@lsqworld
Copy link
Author

lsqworld commented Apr 6, 2017

I feel so sorry for wasted your time! @buixor

@lsqworld lsqworld closed this as completed Apr 6, 2017
@buixor
Copy link
Contributor

buixor commented Apr 6, 2017

Nah, don't worry, doc is a bit slacky !

@buixor
Copy link
Contributor

buixor commented Apr 6, 2017

@jvoisin jvoisin added this to the 0.56 milestone Apr 7, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants