From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org, Saloni.Jain@kpit.com
Subject: Re: [poky][master][PATCH] bzip2: Fix CVE-2019-12900
Date: Wed, 15 Jan 2020 16:30:48 +0000 [thread overview]
Message-ID: <5b486535-37df-28d0-76fd-34c325c8e8db@intel.com> (raw)
In-Reply-To: <1579103247-31173-1-git-send-email-Saloni.Jain@kpit.com>
On 15/01/2020 15:47, Saloni Jain wrote:
> From: Sana Kazi <Sana.Kazi@kpit.com>
>
> Added patch for CVE-2019-12900 as backport from upstream.
> Fixes out of bound access discovered while fuzzying karchive.
>
> Tested by: Sana.Kazi@kpit.com
>
> Signed-off-by: Saloni Jain <Saloni.Jain@kpit.com>
Need a S-o-b in the patch itself alongside a CVE tag, but also why not a
backport for Warrior and Thud?
Ross
next prev parent reply other threads:[~2020-01-15 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 15:47 [poky][master][PATCH] bzip2: Fix CVE-2019-12900 Saloni Jain
2020-01-15 16:02 ` ✗ patchtest: failure for bzip2: Fix CVE-2019-12900 (rev4) Patchwork
2020-01-15 16:30 ` Ross Burton [this message]
2020-01-17 13:14 ` [poky][master][PATCH] bzip2: Fix CVE-2019-12900 Saloni Jain
-- strict thread matches above, loose matches on Subject: below --
2020-01-17 12:57 Saloni Jain
2020-01-21 6:24 Saloni Jain
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=5b486535-37df-28d0-76fd-34c325c8e8db@intel.com \
--to=ross.burton@intel.com \
--cc=Saloni.Jain@kpit.com \
--cc=openembedded-core@lists.openembedded.org \
/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