Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] asterisk: security bump to version 14.7.5
Date: Mon, 8 Jan 2018 20:59:26 +0100	[thread overview]
Message-ID: <20180108205926.39961fa0@windsurf> (raw)
In-Reply-To: <20180108100815.16770-1-peter@korsgaard.com>

Hello,

On Mon,  8 Jan 2018 11:08:15 +0100, Peter Korsgaard wrote:
> Fixes the following security issues:
> 
> * AST-2017-014: Crash in PJSIP resource when missing a contact header A
>   select set of SIP messages create a dialog in Asterisk.  Those SIP
>   messages must contain a contact header.  For those messages, if the header
>   was not present and using the PJSIP channel driver, it would cause
>   Asterisk to crash.  The severity of this vulnerability is somewhat
>   mitigated if authentication is enabled.  If authentication is enabled a
>   user would have to first be authorized before reaching the crash point.
> 
> For more details, see the announcement:
> https://www.asterisk.org/downloads/asterisk-news/asterisk-13185-1475-1515-and-1318-cert2-now-available-security
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
>  package/asterisk/asterisk.hash | 2 +-
>  package/asterisk/asterisk.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

  reply	other threads:[~2018-01-08 19:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 10:08 [Buildroot] [PATCH] asterisk: security bump to version 14.7.5 Peter Korsgaard
2018-01-08 19:59 ` Thomas Petazzoni [this message]
2018-01-16 19:37 ` 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=20180108205926.39961fa0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox