Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@kernel.org>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [sumo] [PATCH v1 1/2] ncurses: CVE-2018-10754
Date: Fri, 5 Oct 2018 00:48:32 -0400	[thread overview]
Message-ID: <3dca9fca-cea6-4830-b28f-805490b3bbfd@kernel.org> (raw)
In-Reply-To: <20181005035515.4922-1-okaya@kernel.org>

On 10/4/2018 11:55 PM, Sinan Kaya wrote:
> * CVE-2018-10754
> A NULL pointer dereference was found in the way the _nc_parse_entry
> function parses terminfo data for compilation. An attacker able to provide
> specially crafted terminfo data could use this flaw to crash the
> application parsing it.
> 
> Affects < 6.1.20180414
> 
> CVE: CVE-2018-10754
> Ref:http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10754
> Signed-off-by: Sinan Kaya<okaya@kernel.org>

Self NAK on this ncurses patch only. This broke docker.
The rest of the patches looked good to me.


      parent reply	other threads:[~2018-10-05  4:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05  3:55 [sumo] [PATCH v1 1/2] ncurses: CVE-2018-10754 Sinan Kaya
2018-10-05  3:55 ` [sumo] [PATCH v1 2/2] git: CVE-2018-11233 Sinan Kaya
2018-10-05  4:48 ` Sinan Kaya [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=3dca9fca-cea6-4830-b28f-805490b3bbfd@kernel.org \
    --to=okaya@kernel.org \
    --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