From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] suricata: Disable sid 2210059.
Date: Thu, 09 Dec 2021 20:17:00 +0100 [thread overview]
Message-ID: <c0f495b0-95af-2cb0-ba0a-94f8f0f32d6c@ipfire.org> (raw)
In-Reply-To: <20211208171805.309048-1-stefan.schantl@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2479 bytes --]
Thank you for working on this.
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> This rule emits a massive logspam and temporary will be disabled until
> a better solution is found.
>
> Fixes #12738.
>
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> lfs/suricata | 1 +
> src/patches/suricata-disable-sid-2210059.patch | 12 ++++++++++++
> 2 files changed, 13 insertions(+)
> create mode 100644 src/patches/suricata-disable-sid-2210059.patch
>
> diff --git a/lfs/suricata b/lfs/suricata
> index 96c2b33fe..6a24a02ab 100644
> --- a/lfs/suricata
> +++ b/lfs/suricata
> @@ -71,6 +71,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> @$(PREBUILD)
> @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
> cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/suricata-5.0-stream-tcp-Handle-retransmitted-SYN-with-TSval.patch
> + cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/suricata-disable-sid-2210059.patch
> cd $(DIR_APP) && LDFLAGS="$(LDFLAGS)" ./configure \
> --prefix=/usr \
> --sysconfdir=/etc \
> diff --git a/src/patches/suricata-disable-sid-2210059.patch b/src/patches/suricata-disable-sid-2210059.patch
> new file mode 100644
> index 000000000..54747dfd2
> --- /dev/null
> +++ b/src/patches/suricata-disable-sid-2210059.patch
> @@ -0,0 +1,12 @@
> +diff -Nur a/rules/stream-events.rules b/rules/stream-events.rules
> +--- a/rules/stream-events.rules 2021-11-17 16:55:12.000000000 +0100
> ++++ b/rules/stream-events.rules 2021-12-08 18:12:39.850189502 +0100
> +@@ -89,7 +89,7 @@
> + # rule to alert if a stream has excessive retransmissions
> + alert tcp any any -> any any (msg:"SURICATA STREAM excessive retransmissions"; flowbits:isnotset,tcp.retransmission.alerted; flowint:tcp.retransmission.count,>=,10; flowbits:set,tcp.retransmission.alerted; classtype:protocol-command-decode; sid:2210054; rev:1;)
> + # Packet on wrong thread. Fires at most once per flow.
> +-alert tcp any any -> any any (msg:"SURICATA STREAM pkt seen on wrong thread"; stream-event:wrong_thread; sid:2210059; rev:1;)
> ++#alert tcp any any -> any any (msg:"SURICATA STREAM pkt seen on wrong thread"; stream-event:wrong_thread; sid:2210059; rev:1;)
> +
> + # Packet with FIN+SYN set
> + alert tcp any any -> any any (msg:"SURICATA STREAM FIN SYN reuse"; stream-event:fin_syn; classtype:protocol-command-decode; sid:2210060; rev:1;)
>
prev parent reply other threads:[~2021-12-09 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 17:18 Stefan Schantl
2021-12-09 16:39 ` Michael Tremer
2021-12-09 19:17 ` Peter Müller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0f495b0-95af-2cb0-ba0a-94f8f0f32d6c@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox