From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"saloni.jain@kpit.com" <saloni.jain@kpit.com>,
"raj.khem@gmail.com" <raj.khem@gmail.com>
Cc: "Rahul.Taya@kpit.com" <Rahul.Taya@kpit.com>,
"anuj.chougule@kpit.com" <anuj.chougule@kpit.com>,
"nisha.parrakat@kpit.com" <nisha.parrakat@kpit.com>
Subject: Re: [OE-core] [poky][zeus][PATCH] libpcre: Add fix for CVE-2020-14155
Date: Thu, 30 Jul 2020 00:10:28 +0000 [thread overview]
Message-ID: <4231da79c401a7314dbdfa3988889f2f38be8060.camel@intel.com> (raw)
In-Reply-To: <1596027345-16076-1-git-send-email-Saloni.Jain@kpit.com>
On Wed, 2020-07-29 at 18:25 +0530, saloni wrote:
> From: Rahul Taya <Rahul.Taya@kpit.com>
>
> Added below patch in libpcre
> CVE-2020-14155.patch
>
> This patch fixes below error:
> PCRE could allow a remote attacker to execute arbitrary
> code on the system, caused by an integer overflow in
> libpcre via a large number after (?C substring.
> By sending a request with a large number, an attacker
> can execute arbitrary code on the system or
> cause the application to crash.
>
> Upstream-Status: Pending
>
> Tested-by: Rahul Taya <Rahul.Taya@kpit.com>
> Signed-off-by: Saloni Jain <Saloni.Jain@kpit.com>
> ---
> .../libpcre/libpcre/CVE-2020-14155.patch | 40
> ++++++++++++++++++++++
> meta/recipes-support/libpcre/libpcre_8.44.bb | 3 +-
zeus has libpcre version 8.43. Also it looks like this specific fix is
already is 8.44.
So please test and send again for proper version & branch.
Thanks,
Anuj
prev parent reply other threads:[~2020-07-30 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 12:55 [poky][zeus][PATCH] libpcre: Add fix for CVE-2020-14155 saloni
2020-07-29 13:02 ` ✗ patchtest: failure for " Patchwork
2020-07-29 17:56 ` [poky][zeus][PATCH] " Khem Raj
2020-07-30 0:10 ` Anuj Mittal [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=4231da79c401a7314dbdfa3988889f2f38be8060.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=Rahul.Taya@kpit.com \
--cc=anuj.chougule@kpit.com \
--cc=nisha.parrakat@kpit.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=saloni.jain@kpit.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 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.