From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Alexander Egorenkov <egorenar-dev@posteo.net>
Subject: Re: [Buildroot] [PATCH] package/multipath-tools: security bump to version 0.9.3
Date: Thu, 03 Nov 2022 15:46:26 +0100 [thread overview]
Message-ID: <87leosp03h.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221103143414.2624696-1-peter@korsgaard.com> (Peter Korsgaard's message of "Thu, 3 Nov 2022 15:34:13 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes the following security issues:
> - CVE-2022-41974: Authorization bypass
> - CVE-2022-41973: Symlink attack
> For more details, see the writeup:
> https://blog.qualys.com/vulnerabilities-threat-research/2022/10/25/leeloo-multipath-authorization-bypass-and-symlink-attack-in-multipathd-cve-2022-41974-and-cve-2022-41973
Ups, that should have been the linked advisory, E.G.:
https://www.qualys.com/2022/10/24/leeloo-multipath/leeloo-multipath.txt
> Update README.md hash after license-unrelated changes:
> git shortlog 0.9.0..0.9.3 -- README.md
> Konstantin Kharlamov (1):
> README.md: mention libreadline and libedit optional deps
> Xose Vazquez Perez (4):
> multipath-tools: update devel repo info in README.md
> multipath-tools: add ALUA info to README.md
> multipath-tools: add basic info on how to use multipath-tools with NVMe devices
> multipath-tools: add more info for NetApp RDAC arrays
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/multipath-tools/multipath-tools.hash | 4 ++--
> package/multipath-tools/multipath-tools.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
> diff --git a/package/multipath-tools/multipath-tools.hash b/package/multipath-tools/multipath-tools.hash
> index df0d24fb74..6f893d37ce 100644
> --- a/package/multipath-tools/multipath-tools.hash
> +++ b/package/multipath-tools/multipath-tools.hash
> @@ -1,7 +1,7 @@
> # Locally computed:
> -sha256 d6d1d819a53d076a91828ede42d9786451a471c4b71ca3fd25d04ad5413e3f95 multipath-tools-0.9.0.tar.gz
> +sha256 7d5af5d86e43b757e253d1ba244aa8a9c09bfbb1677a72accb799b1bfcc0a9ac multipath-tools-0.9.3.tar.gz
> sha256 8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643 LICENSES/GPL-2.0
> sha256 3972dc9744f6499f0f9b2dbf76696f2ae7ad8af9b23dde66d6af86c9dfb36986 LICENSES/GPL-3.0
> sha256 b7993225104d90ddd8024fd838faf300bea5e83d91203eab98e29512acebd69c LICENSES/LGPL-2.0
> sha256 dc626520dcd53a22f727af3ee42c770e56c97a64fe3adb063799d8ab032fe551 LICENSES/LGPL-2.1
> -sha256 fb0a5d2008c609fec129d2ffd01dd7f65f0e3868bcf465b6fda76e25ff896ce9 README.md
> +sha256 1e6095ac219062b8ddb2416d2a3cc40560619cd6b3ba609f5602bbd320413be0 README.md
> diff --git a/package/multipath-tools/multipath-tools.mk b/package/multipath-tools/multipath-tools.mk
> index f3ce3ca8b8..ec5d853644 100644
> --- a/package/multipath-tools/multipath-tools.mk
> +++ b/package/multipath-tools/multipath-tools.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
> -MULTIPATH_TOOLS_VERSION = 0.9.0
> +MULTIPATH_TOOLS_VERSION = 0.9.3
> MULTIPATH_TOOLS_SITE = $(call github,opensvc,multipath-tools,$(MULTIPATH_TOOLS_VERSION))
> MULTIPATH_TOOLS_LICENSE = \
> --
> 2.30.2
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-11-03 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 14:34 [Buildroot] [PATCH] package/multipath-tools: security bump to version 0.9.3 Peter Korsgaard
2022-11-03 14:46 ` Peter Korsgaard [this message]
2022-11-03 22:06 ` Thomas Petazzoni via buildroot
2022-11-14 7:20 ` 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=87leosp03h.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=egorenar-dev@posteo.net \
/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