From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Ovidiu Panait <ovidiu.panait@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] git: CVE-2017-14867
Date: Tue, 24 Oct 2017 12:01:38 +0300 [thread overview]
Message-ID: <8bb8f1fc-7dfd-8ce1-891b-e8d60f83b927@linux.intel.com> (raw)
In-Reply-To: <20171023173916.271270-1-ovidiu.panait@windriver.com>
On 10/23/2017 08:39 PM, Ovidiu Panait wrote:
> Git before 2.10.5, 2.11.x before 2.11.4, 2.12.x before 2.12.5, 2.13.x before
> 2.13.6, and 2.14.x before 2.14.2 uses unsafe Perl scripts to support
> subcommands such as cvsserver, which allows attackers to execute arbitrary
> OS commands via shell metacharacters in a module name. The vulnerable code
> is reachable via git-shell even without CVS support.
It's better to simply update the recipe to the latest version that does
not have the vulnerability, can you do that please?
Alex
prev parent reply other threads:[~2017-10-24 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 17:39 [PATCH] git: CVE-2017-14867 Ovidiu Panait
2017-10-23 18:03 ` ✗ patchtest: failure for " Patchwork
2017-10-23 19:22 ` Leonardo Sandoval
2017-10-24 9:01 ` Alexander Kanavin [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=8bb8f1fc-7dfd-8ce1-891b-e8d60f83b927@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ovidiu.panait@windriver.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