From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libglib2: security bump to version 2.66.7
Date: Sat, 13 Mar 2021 15:39:36 +0100 [thread overview]
Message-ID: <87y2er3yon.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210227090424.429843-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 27 Feb 2021 10:04:24 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> - Fix CVE-2021-27218: An issue was discovered in GNOME GLib before
> 2.66.7 and 2.67.x before 2.67.4. If g_byte_array_new_take() was called
> with a buffer of 4GB or more on a 64-bit platform, the length would be
> truncated modulo 2**32, causing unintended length truncation.
> - Fix CVE-2021-27219: An issue was discovered in GNOME GLib before
> 2.66.6 and 2.67.x before 2.67.3. The function g_bytes_new has an
> integer overflow on 64-bit platforms due to an implicit cast from 64
> bits to 32 bits. The overflow could potentially lead to memory
> corruption.
For 2020.02.x / 2020.11.x I have instead backported the CVE-2021.27218
fix. The CVE-2021-27219 fix adds a g_memdup2() function and changes a
bunch of callers to use that instead of g_memdup(), which is not quite
trivial to backport, so I have left that for now.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2021-03-13 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 9:04 [Buildroot] [PATCH 1/1] package/libglib2: security bump to version 2.66.7 Fabrice Fontaine
2021-02-27 15:56 ` Yann E. MORIN
2021-03-13 14:39 ` Peter Korsgaard [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=87y2er3yon.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.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 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.