From: Peter Korsgaard <peter@korsgaard.com>
To: Frank Vanbever via buildroot <buildroot@buildroot.org>
Cc: Frank Vanbever <frank.vanbever@mind.be>
Subject: Re: [Buildroot] [PATCH 2023.02.x] package/libmodsecurity: backport security fix for CVE-2023-28882
Date: Sat, 26 Aug 2023 22:06:23 +0200 [thread overview]
Message-ID: <87il917em8.fsf@48ers.dk> (raw)
In-Reply-To: <20230713161139.182388-1-frank.vanbever@mind.be> (Frank Vanbever via buildroot's message of "Thu, 13 Jul 2023 18:11:39 +0200")
>>>>> "Frank" == Frank Vanbever via buildroot <buildroot@buildroot.org> writes:
> Fixes the following issue:
> - CVE-2023-28882: Trustwave ModSecurity 3.0.5 through 3.0.8 before 3.0.9 allows
> a denial of service (worker crash and unresponsiveness) because some inputs
> cause a segfault in the Transaction class for some configurations.
> https://security-tracker.debian.org/tracker/CVE-2023-28882
> Signed-off-by: Frank Vanbever <frank.vanbever@mind.be>
Sorry for the slow response.
We are using 3.0.8 on 2023.02.x. Is the delta between 3.0.8 and 3.0.9 so
big that it makes sense to add this patch rather than just bumping to
3.0.9 - Especially given that 3.0.10 contained another security fix?
Looking at the 3.0.9 release notes, it seems to be almost entirely
fixes:
https://github.com/SpiderLabs/ModSecurity/releases/tag/v3.0.9
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-26 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 16:11 [Buildroot] [PATCH 2023.02.x] package/libmodsecurity: backport security fix for CVE-2023-28882 Frank Vanbever via buildroot
2023-08-26 20:06 ` Peter Korsgaard [this message]
2023-08-30 7:29 ` Frank Vanbever via buildroot
2023-08-30 8:13 ` Peter Korsgaard
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=87il917em8.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=frank.vanbever@mind.be \
/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