From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ntfs-3g: security bump to version 2022.10.3
Date: Sun, 13 Nov 2022 22:17:58 +0100 [thread overview]
Message-ID: <20221113221758.54889e0b@windsurf> (raw)
In-Reply-To: <20221112213655.110226-1-fontaine.fabrice@gmail.com>
On Sat, 12 Nov 2022 22:36:55 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix CVE-2022-40284: A buffer overflow was discovered in NTFS-3G before
> 2022.10.3. Crafted metadata in an NTFS image can cause code execution. A
> local attacker can exploit this if the ntfs-3g binary is setuid root. A
> physically proximate attacker can exploit this if NTFS-3G software is
> configured to execute upon attachment of an external storage device.
>
> https://github.com/tuxera/ntfs-3g/security/advisories/GHSA-v4w8-jv3w-7prm
> https://github.com/tuxera/ntfs-3g/releases/tag/2022.10.3
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/ntfs-3g/ntfs-3g.hash | 2 +-
> package/ntfs-3g/ntfs-3g.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
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-11-13 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 21:36 [Buildroot] [PATCH 1/1] package/ntfs-3g: security bump to version 2022.10.3 Fabrice Fontaine
2022-11-13 21:17 ` Thomas Petazzoni via buildroot [this message]
2022-11-15 13: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=20221113221758.54889e0b@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.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.