mirror of https://github.com/OISF/suricata
tls: fix negated match
A negated match is matching if the tested field is NULL. But as it is not set, nor negated nor normal test must match. Without this patch, a rule like: alert tls any any -> any any (msg:"negated match"; tls.subject:!"CN=home.regit.org"; sid:1; rev:1;) is alerting for all connections. Event if they are done on a certificate with matching subject. This was due to the fact that tls protocol is discovered before the handshake is complete. Thus the condition on tls is true with a NULL tls.subject. And code was returning a positive match in the case of a NULL subject and a signature with a negated match.pull/808/merge
parent
385c04164b
commit
c2fcf329f0
Loading…
Reference in New Issue