From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] expat: Version bump. 2.6.2 -> 2.6.3
Date: Thu, 12 Sep 2024 14:12:19 +0200 [thread overview]
Message-ID: <20240912121219.2689095-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20240905170558.3529176-1-christian.melki@t2data.com>
Thanks, applied as 30ee313b4e2c3bf0475db38c75f859352a3ad332.
Michael
[sent from post-receive hook]
On Thu, 12 Sep 2024 14:12:19 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Mainly security fixes.
> https://github.com/libexpat/libexpat/blob/R_2_6_3/expat/Changes
>
> Plugs CVEs:
> CVE-2024-45490 - An issue was discovered in libexpat before 2.6.3. xmlparse.c does not reject a negative length for XML_ParseBuffer.
> CVE-2024-45491 - Internal function dtdCopy can have an integer overflow for nDefaultAtts on 32-bit platforms.
> CVE-2024-45492 - Internal function nextScaffoldPart can have an integer overflow for m_groupSize on 32-bit platforms.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20240905170558.3529176-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/expat.make b/rules/expat.make
> index 03f9ac6b4d40..31afb8604eae 100644
> --- a/rules/expat.make
> +++ b/rules/expat.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_EXPAT) += expat
> #
> # Paths and names
> #
> -EXPAT_VERSION := 2.6.2
> -EXPAT_MD5 := b246f58b25a7629fca6cbd1429400cdf
> +EXPAT_VERSION := 2.6.3
> +EXPAT_MD5 := c70040a3f2743d9645cb029d3c9a7c89
> EXPAT := expat-$(EXPAT_VERSION)
> EXPAT_SUFFIX := tar.bz2
> EXPAT_RELEASE := R_$(subst .,_,$(EXPAT_VERSION))
prev parent reply other threads:[~2024-09-12 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 17:05 [ptxdist] [PATCH] " Christian Melki
2024-09-12 12:12 ` Michael Olbrich [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=20240912121219.2689095-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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