From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/mongodb: security bump to version 4.2.18
Date: Wed, 26 Jan 2022 23:33:24 +0100 [thread overview]
Message-ID: <20220126233324.523b01d9@windsurf> (raw)
In-Reply-To: <20220125173422.3476090-1-fontaine.fabrice@gmail.com>
On Tue, 25 Jan 2022 18:34:22 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix CVE-2021-20330: An attacker with basic CRUD permissions on a
> replicated collection can run the applyOps command with specially
> malformed oplog entries, resulting in a potential denial of service on
> secondaries. This issue affects MongoDB Server v4.0 versions prior to
> 4.0.25; MongoDB Server v4.2 versions prior to 4.2.14; MongoDB Server
> v4.4 versions prior to 4.4.6.
>
> Drop third patch (already in version)
>
> https://docs.mongodb.com/master/release-notes/4.2/
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...-MINSIGSTKSZ-is-no-longer-a-constant.patch | 49 -------------------
> package/mongodb/mongodb.hash | 2 +-
> package/mongodb/mongodb.mk | 2 +-
> 3 files changed, 2 insertions(+), 51 deletions(-)
> delete mode 100644 package/mongodb/0003-SERVER-59459-With-glibc-2-34-MINSIGSTKSZ-is-no-longer-a-constant.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-26 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 17:34 [Buildroot] [PATCH 1/1] package/mongodb: security bump to version 4.2.18 Fabrice Fontaine
2022-01-26 22:33 ` Thomas Petazzoni [this message]
2022-01-28 21:17 ` 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=20220126233324.523b01d9@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.