Suricata rule load errors: abuse.ch/URLhaus

Started by dinguz, October 18, 2019, 07:42:53 PM

Previous topic - Next topic
October 18, 2019, 07:42:53 PM Last Edit: October 22, 2019, 07:22:43 PM by dinguz
I'm seeing these errors lateley:

Oct 18 00:01:57 haanjdj suricata[20436]: [100108] <Error> -- [ERRCODE: SC_ERR_INVALID_SIGNATURE(39)] - error parsing signature "alert http $HOME_NET any -> $EXTERNAL_NET any (msg:"URLhaus Known malware download URL detected"; flow:established,from_client; content:"GET"; http_method; content:"/wp-content/gmi97ucro9sv7to01wm6gb|/"; http_uri; depth:36; isdataat:!1,relative; content:"artopinvest.ro"; http_host; depth:14; isdataat:!1,relative; metadata:created_at 2019_10_11; reference:url, urlhaus.abuse.ch/url/243894/; classtype:trojan-activity;sid:81106994; rev:1;)" from file /usr/local/etc/suricata/opnsense.rules/abuse.ch.urlhaus.rules at line 1783

They always involve the abuse.ch.urlhaus.rules file. I have compared the faulty entries, and I believe the problem to be the pipe symbol ('|') in for example the entry 'content:"/wp-content/gmi97ucro9sv7to01wm6gb|/"'; it shouldn't be there.

Is this an upstream problem that should be reported there, or is this something that should be dealt with within Opnsense?
Note: This post may have been lightly edited by AI for spelling and minor readability improvements. The content and findings are entirely my own.

Hi,

This should be reported upstream, i think.


5.0.1 should be due this November, we try to pick it up and release Suricata 5 to the production track at the same time. So whatever gets reported upstream will be in the update sooner. :)


Cheers,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

I haven't found a possibliy to file a bug. I contacted them by mail. Hopefully it gets fixed.

wow, those guys are quick. Got a short response, should be solved. Can anyone test?