From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann <marcus.hoffmann@othermo.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/xz: backport CVE-2022-1271 security fix
Date: Tue, 19 Apr 2022 19:47:39 +0300 [thread overview]
Message-ID: <87tuapqaqw.fsf@tarshish> (raw)
In-Reply-To: <20220419111714.1647112-2-marcus.hoffmann@othermo.de>
Hi Marcus,
On Tue, Apr 19 2022, Marcus Hoffmann wrote:
> Fixes the following security issue:
>
> CVE-2022-1271/ZDI-22-619/ZDI-CAN-16587: arbitrary-file-write vulnerability
>
> Malicious filenames can make xzgrep to write to arbitrary files
> or (with a GNU sed extension) lead to arbitrary code execution.
>
> xzgrep from XZ Utils versions up to and including 5.2.5 are
> affected. 5.3.1alpha and 5.3.2alpha are affected as well.
> This patch works for all of them.
>
> This bug was inherited from gzip's zgrep. gzip 1.12 includes
> a fix for zgrep.
>
> This vulnerability was discovered by:
> cleemy desu wayo working with Trend Micro Zero Day Initiative
>
> https://www.mail-archive.com/xz-devel@tukaani.org/msg00551.html
> https://www.zerodayinitiative.com/advisories/ZDI-22-619/
> https://www.openwall.com/lists/oss-security/2022/04/07/8
> Signed-off-by: Marcus Hoffmann <marcus.hoffmann@othermo.de>
> ---
> package/xz/0001-xzgrep-ZDI-CAN-16587.patch | 96 ++++++++++++++++++++++
> 1 file changed, 96 insertions(+)
> create mode 100644 package/xz/0001-xzgrep-ZDI-CAN-16587.patch
This patch should also add XZ_IGNORE_CVES in xz.mk.
baruch
>
> diff --git a/package/xz/0001-xzgrep-ZDI-CAN-16587.patch b/package/xz/0001-xzgrep-ZDI-CAN-16587.patch
> new file mode 100644
> index 0000000000..78ee9640f0
> --- /dev/null
> +++ b/package/xz/0001-xzgrep-ZDI-CAN-16587.patch
> @@ -0,0 +1,96 @@
> +From 69d1b3fc29677af8ade8dc15dba83f0589cb63d6 Mon Sep 17 00:00:00 2001
> +From: Lasse Collin <lasse.collin@tukaani.org>
> +Date: Tue, 29 Mar 2022 19:19:12 +0300
> +Subject: [PATCH] xzgrep: Fix escaping of malicious filenames (ZDI-CAN-16587).
> +
> +Malicious filenames can make xzgrep to write to arbitrary files
> +or (with a GNU sed extension) lead to arbitrary code execution.
> +
> +xzgrep from XZ Utils versions up to and including 5.2.5 are
> +affected. 5.3.1alpha and 5.3.2alpha are affected as well.
> +This patch works for all of them.
> +
> +This bug was inherited from gzip's zgrep. gzip 1.12 includes
> +a fix for zgrep.
> +
> +The issue with the old sed script is that with multiple newlines,
> +the N-command will read the second line of input, then the
> +s-commands will be skipped because it's not the end of the
> +file yet, then a new sed cycle starts and the pattern space
> +is printed and emptied. So only the last line or two get escaped.
> +
> +One way to fix this would be to read all lines into the pattern
> +space first. However, the included fix is even simpler: All lines
> +except the last line get a backslash appended at the end. To ensure
> +that shell command substitution doesn't eat a possible trailing
> +newline, a colon is appended to the filename before escaping.
> +The colon is later used to separate the filename from the grep
> +output so it is fine to add it here instead of a few lines later.
> +
> +The old code also wasn't POSIX compliant as it used \n in the
> +replacement section of the s-command. Using \<newline> is the
> +POSIX compatible method.
> +
> +LC_ALL=C was added to the two critical sed commands. POSIX sed
> +manual recommends it when using sed to manipulate pathnames
> +because in other locales invalid multibyte sequences might
> +cause issues with some sed implementations. In case of GNU sed,
> +these particular sed scripts wouldn't have such problems but some
> +other scripts could have, see:
> +
> + info '(sed)Locale Considerations'
> +
> +This vulnerability was discovered by:
> +cleemy desu wayo working with Trend Micro Zero Day Initiative
> +
> +Thanks to Jim Meyering and Paul Eggert discussing the different
> +ways to fix this and for coordinating the patch release schedule
> +with gzip.
> +
> +Signed-off-by: Marcus Hoffmann <marcus.hoffmann@othermo.de>
> +---
> + src/scripts/xzgrep.in | 20 ++++++++++++--------
> + 1 file changed, 12 insertions(+), 8 deletions(-)
> +
> +diff --git a/src/scripts/xzgrep.in b/src/scripts/xzgrep.in
> +index b180936..e5186ba 100644
> +--- a/src/scripts/xzgrep.in
> ++++ b/src/scripts/xzgrep.in
> +@@ -180,22 +180,26 @@ for i; do
> + { test $# -eq 1 || test $no_filename -eq 1; }; then
> + eval "$grep"
> + else
> ++ # Append a colon so that the last character will never be a newline
> ++ # which would otherwise get lost in shell command substitution.
> ++ i="$i:"
> ++
> ++ # Escape & \ | and newlines only if such characters are present
> ++ # (speed optimization).
> + case $i in
> + (*'
> + '* | *'&'* | *'\'* | *'|'*)
> +- i=$(printf '%s\n' "$i" |
> +- sed '
> +- $!N
> +- $s/[&\|]/\\&/g
> +- $s/\n/\\n/g
> +- ');;
> ++ i=$(printf '%s\n' "$i" | LC_ALL=C sed 's/[&\|]/\\&/g; $!s/$/\\/');;
> + esac
> +- sed_script="s|^|$i:|"
> ++
> ++ # $i already ends with a colon so don't add it here.
> ++ sed_script="s|^|$i|"
> +
> + # Fail if grep or sed fails.
> + r=$(
> + exec 4>&1
> +- (eval "$grep" 4>&-; echo $? >&4) 3>&- | sed "$sed_script" >&3 4>&-
> ++ (eval "$grep" 4>&-; echo $? >&4) 3>&- |
> ++ LC_ALL=C sed "$sed_script" >&3 4>&-
> + ) || r=2
> + exit $r
> + fi >&3 5>&-
> +--
> +2.35.1
> +
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-04-19 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 11:17 [Buildroot] [PATCH 1/2] package/gzip: security bump to 1.12 Marcus Hoffmann
2022-04-19 11:17 ` [Buildroot] [PATCH 2/2] package/xz: backport CVE-2022-1271 security fix Marcus Hoffmann
2022-04-19 16:47 ` Baruch Siach via buildroot [this message]
2022-04-19 17:27 ` Marcus Hoffmann
2022-04-19 17:37 ` Marcus Hoffmann
2022-04-19 20:31 ` [Buildroot] [PATCH 1/2] package/gzip: security bump to 1.12 Arnout Vandecappelle
2022-05-22 10:30 ` 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=87tuapqaqw.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=marcus.hoffmann@othermo.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