From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] irssi: security bump to version 1.0.6
Date: Sun, 7 Jan 2018 23:47:56 +0100 [thread overview]
Message-ID: <20180107234756.473f5ebe@windsurf> (raw)
In-Reply-To: <20180107210318.15006-1-peter@korsgaard.com>
Hello,
On Sun, 7 Jan 2018 22:03:18 +0100, Peter Korsgaard wrote:
> From the advisory (https://irssi.org/security/irssi_sa_2018_01.txt):
>
> Multiple vulnerabilities have been located in Irssi.
>
> (a) When the channel topic is set without specifying a sender, Irssi
> may dereference NULL pointer. Found by Joseph Bisch. (CWE-476)
>
> CVE-2018-5206 was assigned to this issue.
>
> (b) When using incomplete escape codes, Irssi may access data beyond
> the end of the string. (CWE-126) Found by Joseph Bisch.
>
> CVE-2018-5205 was assigned to this issue.
>
> (c) A calculation error in the completion code could cause a heap
> buffer overflow when completing certain strings. (CWE-126) Found
> by Joseph Bisch.
>
> CVE-2018-5208 was assigned to this issue.
>
> (d) When using an incomplete variable argument, Irssi may access data
> beyond the end of the string. (CWE-126) Found by Joseph Bisch.
>
> CVE-2018-5207 was assigned to this issue.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/irssi/irssi.hash | 2 +-
> package/irssi/irssi.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-07 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 21:03 [Buildroot] [PATCH] irssi: security bump to version 1.0.6 Peter Korsgaard
2018-01-07 22:47 ` Thomas Petazzoni [this message]
2018-01-08 21:54 ` Peter Korsgaard
2018-01-30 12:20 ` 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=20180107234756.473f5ebe@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.