Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/expat: security bump to version 2.4.5
Date: Sun, 20 Feb 2022 10:55:54 +0100	[thread overview]
Message-ID: <20220220095554.GQ522310@scaer> (raw)
In-Reply-To: <20220219122831.2961097-2-fontaine.fabrice@gmail.com>

Fabrice, All,

On 2022-02-19 13:28 +0100, Fabrice Fontaine spake thusly:
> Security fixes:
>  #562  CVE-2022-25235 -- Passing malformed 2- and 3-byte UTF-8
>        sequences (e.g. from start tag names) to the XML
>        processing application on top of Expat can cause
>        arbitrary damage (e.g. code execution) depending
>        on how invalid UTF-8 is handled inside the XML
>        processor; validation was not their job but Expat's.
>        Exploits with code execution are known to exist.
>  #561  CVE-2022-25236 -- Passing (one or more) namespace separator
>        characters in "xmlns[:prefix]" attribute values
>        made Expat send malformed tag names to the XML
>        processor on top of Expat which can cause
>        arbitrary damage (e.g. code execution) depending
>        on such unexpectable cases are handled inside the XML
>        processor; validation was not their job but Expat's.
>        Exploits with code execution are known to exist.
>  #558  CVE-2022-25313 -- Fix stack exhaustion in doctype parsing
>        that could be triggered by e.g. a 2 megabytes
>        file with a large number of opening braces.
>        Expected impact is denial of service or potentially
>        arbitrary code execution.
>  #560  CVE-2022-25314 -- Fix integer overflow in function copyString;
>        only affects the encoding name parameter at parser creation
>        time which is often hardcoded (rather than user input),
>        takes a value in the gigabytes to trigger, and a 64-bit
>        machine.  Expected impact is denial of service.
>  #559  CVE-2022-25315 -- Fix integer overflow in function storeRawNames;
>        needs input in the gigabytes and a 64-bit machine.
>        Expected impact is denial of service or potentially
>        arbitrary code execution.
> 
> https://blog.hartwork.org/posts/expat-2-4-5-released/
> https://github.com/libexpat/libexpat/blob/R_2_4_5/expat/Changes
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/expat/expat.hash | 8 ++++----
>  package/expat/expat.mk   | 2 +-
>  2 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/package/expat/expat.hash b/package/expat/expat.hash
> index a6f43af291..cd2e8c7fb9 100644
> --- a/package/expat/expat.hash
> +++ b/package/expat/expat.hash
> @@ -1,7 +1,7 @@
> -# From https://sourceforge.net/projects/expat/files/expat/2.4.4/
> -md5  a712d23b7afb32e7527cf0b3fd8f12ac  expat-2.4.4.tar.xz
> -sha1  6028b04d3505fc519c4c7c6bd67e1ad1a08cd7b6  expat-2.4.4.tar.xz
> +# From https://sourceforge.net/projects/expat/files/expat/2.4.5/
> +md5  9dc183e6c1eebc1b658c1e71be0885e1  expat-2.4.5.tar.xz
> +sha1  360a49b55c442e91cb7b328bc0335083909ddf4f  expat-2.4.5.tar.xz
>  
>  # Locally calculated
> -sha256  b1f9f1b1a5ebb0acaa88c9ff79bfa4e145823b78aa5185e5c5d85f060824778a  expat-2.4.4.tar.xz
> +sha256  f2af8fc7cdc63a87920da38cd6d12cb113c3c3a3f437495b1b6541e0cff32579  expat-2.4.5.tar.xz
>  sha256  8c6b5b6de8fae20b317f4992729abc0e520bfba4c7606cd1e9eeb87418eebdec  COPYING
> diff --git a/package/expat/expat.mk b/package/expat/expat.mk
> index 250600c25e..7815d61027 100644
> --- a/package/expat/expat.mk
> +++ b/package/expat/expat.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -EXPAT_VERSION = 2.4.4
> +EXPAT_VERSION = 2.4.5
>  EXPAT_SITE = http://downloads.sourceforge.net/project/expat/expat/$(EXPAT_VERSION)
>  EXPAT_SOURCE = expat-$(EXPAT_VERSION).tar.xz
>  EXPAT_INSTALL_STAGING = YES
> -- 
> 2.34.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-02-20  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19 12:28 [Buildroot] [PATCH 1/2] package/expat: fix tarball sha256 Fabrice Fontaine
2022-02-19 12:28 ` [Buildroot] [PATCH 2/2] package/expat: security bump to version 2.4.5 Fabrice Fontaine
2022-02-20  9:55   ` Yann E. MORIN [this message]
2022-03-10 19:38   ` Peter Korsgaard
2022-02-20  9:54 ` [Buildroot] [PATCH 1/2] package/expat: fix tarball sha256 Yann E. MORIN

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=20220220095554.GQ522310@scaer \
    --to=yann.morin.1998@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox