[asterisk-users] AST-2019-005: Remote Crash Vulnerability in audio transcoding

2019-09-05 Thread Asterisk Security Team
   Asterisk Project Security Advisory - AST-2019-005

  Product Asterisk
  Summary Remote Crash Vulnerability in audio transcoding 
 Nature of Advisory   Denial of Service   
   Susceptibility Remote Unauthenticated Sessions 
  SeverityMinor   
   Exploits Known No  
Reported On   August 7, 2019  
Reported By   Gregory Massel  
 Posted On
  Last Updated On August 26, 2019 
  Advisory ContactJcolp AT sangoma DOT com
  CVE NameCVE-2019-15639  

  Description When audio frames are given to the audio transcoding
  support in Asterisk the number of samples are examined  
  and as part of this a message is output to indicate 
  that no samples are present. A change was done to   
  suppress this message for a particular scenario in  
  which the message was not relevant. This change 
  assumed that information about the origin of a frame
  will always exist when in reality it may not.   
  
  This issue presented itself when an RTP packet  
  containing no audio (and thus no samples) was   
  received. In a particular transcoding scenario this 
  audio frame would get turned into a frame with no   
  origin information. If this new frame was then given
  to the audio transcoding support a crash would occur
  as no samples and no origin information would be
  present. The transcoding scenario requires the  
  “genericplc” option to be set to enabled (the 
default)  
  and a transcoding path from the source format into  
  signed linear and then from signed linear into another  
  format. 
  
  Note that there may be other scenarios that have not
  been found which can cause an audio frame with no   
  origin to be given to the audio transcoding support 
  and thus cause a crash. 
Modules Affected  main/translate.c

Resolution  The “genericplc” option can be disabled in codecs.conf to   
  
mitigate the described scenario. It is recommended, however,  
that Asterisk be upgraded to one of the listed versions or
the linked patch applied to protect against potential 
unknown scenarios.

   Affected Versions
 Product   Release Series  
  Asterisk Open Source  13.x   13.28.0
  Asterisk Open Source  16.x   16.5.0 

  Corrected In  
 Product  Release 
   Asterisk Open Source   13.28.1 
   Asterisk Open Source16.5.1 

Patches
   SVN URL  Revision  
   http://downloads.asterisk.org/pub/security/AST-2019-005-13.diff Asterisk   
   13 
   http://downloads.asterisk.org/pub/security/AST-2019-005-16.diff Asterisk   
   16 

   Links https://issues.asterisk.org/jira/browse/ASTERISK-28499   

Asterisk Project Security Advisories are posted at
http://www.asterisk.org/security  
  
This document may be superseded by later versions; if so, the latest  
version will be posted at 

[asterisk-users] AST-2019-004: Crash when negotiating for T.38 with a declined stream

2019-09-05 Thread Asterisk Security Team
   Asterisk Project Security Advisory - AST-2019-004

 ProductAsterisk  
 SummaryCrash when negotiating for T.38 with a declined   
stream
Nature of Advisory  Remote Crash  
  SusceptibilityRemote Authenticated Sessions 
 Severity   Minor 
  Exploits KnownNo
   Reported On  August 05, 2019   
   Reported By  Alexei Gradinari  
Posted On   September 05, 2019
 Last Updated OnSeptember 4, 2019 
 Advisory Contact   kharwell AT sangoma DOT com   
 CVE Name   CVE-2019-15297

  Description When Asterisk sends a re-invite initiating T.38 
  faxing, and the endpoint responds with a declined   
  media stream a crash will then occur in Asterisk.   
Modules Affected  res_pjsip_t38.c 

Resolution  If T.38 faxing is not required then setting the “t38_udptl” 
  
configuration option on the endpoint to “no” disables this  
  
functionality. This option defaults to “no” so you have to  
  
have explicitly set it “yes” to potentially be affected by  
  
this issue.   
  
Otherwise, if T.38 faxing is required then Asterisk should
be upgraded to a fixed version.   

   Affected Versions
Product  Release Series  
 Asterisk Open Source 15.x   All releases 
 Asterisk Open Source 16.x   All releases 

  Corrected In
Product  Release  
 Asterisk Open Source 15.7.4,16.5.1   

Patches
   SVN URL  Revision  
   http://downloads.asterisk.org/pub/security/AST-2019-004-15.diff Asterisk   
   15 
   http://downloads.asterisk.org/pub/security/AST-2019-004-16.diff Asterisk   
   16 

   Links https://issues.asterisk.org/jira/browse/ASTERISK-28495   

Asterisk Project Security Advisories are posted at
http://www.asterisk.org/security  
  
This document may be superseded by later versions; if so, the latest  
version will be posted at 
http://downloads.digium.com/pub/security/AST-2019-004.pdf and 
http://downloads.digium.com/pub/security/AST-2019-004.html

Revision History
  Date  Editor Revisions Made 
August 28, 2019Kevin Harwell Initial revision 

   Asterisk Project Security Advisory - AST-2019-004
   Copyright © 2019 Digium, Inc. All Rights Reserved.
  Permission is hereby granted to distribute and publish this advisory in its
   original, unaltered form.

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

Check out the new Asterisk community forum at: https://community.asterisk.org/

New to Asterisk? Start here:
  https://wiki.asterisk.org/wiki/display/AST/Getting+Started

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

[asterisk-users] Asterisk 13.28.1, 15.7.4 and 16.5.1 Now Available (Security)

2019-09-05 Thread Asterisk Development Team
The Asterisk Development Team would like to announce security releases for
Asterisk 13, 15 and 16. The available releases are released as versions 13.28.1,
15.7.4 and 16.5.1.

These releases are available for immediate download at

https://downloads.asterisk.org/pub/telephony/asterisk/releases

The following security vulnerabilities were resolved in these versions:

* AST-2019-004: Crash when negotiating for T.38 with a declined stream
  When Asterisk sends a re-invite initiating T.38 faxing, and the endpoint
  responds with a declined media stream a crash will then occur in Asterisk.

* AST-2019-005: Remote Crash Vulnerability in audio transcoding
  When audio frames are given to the audio transcoding support in Asterisk the
  number of samples are examined and as part of this a message is output to
  indicate that no samples are present. A change was done to suppress this
  message for a particular scenario in which the message was not relevant. This
  change assumed that information about the origin of a frame will always exist
  when in reality it may not.

For a full list of changes in the current releases, please see the ChangeLogs:

https://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-13.28.1
https://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-15.7.4
https://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-16.5.1

The security advisories are available at:

https://downloads.asterisk.org/pub/security/AST-2019-004.pdf
https://downloads.asterisk.org/pub/security/AST-2019-005.pdf

Thank you for your continued support of Asterisk!-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

Check out the new Asterisk community forum at: https://community.asterisk.org/

New to Asterisk? Start here:
  https://wiki.asterisk.org/wiki/display/AST/Getting+Started

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] asterisk-users Digest, Vol 181, Issue 3

2019-09-05 Thread Tony Mountifield
In article <874506323.2924334.1567645810...@mail.yahoo.com>,
bilal ghayyad  wrote:
> 
>  Thank you a lot for your kindly help and reply. Actually it helped me a 
> lot.I was using _X. in the extensions.conf at
> the trunkinbound context.Can you advise me what is the difference between _X. 
> and s? In other words, when it is better
> to use s and when it is better to use _X.?
> Again, I am fully thanks for you.RegardsBilal

They do different things.

_X. will match any extension number beginning with a digit. This is what
you would normally use to match incoming calls that specify a number,
and is presumably what you have already.

s will only match is no extension number is given. This would be the case
for an analogue line, for example, or a SIP connection that didn't give
a destination number. It is also matched for OPTIONS requests used to
handle "qualify".

So in your [trunkinbound] context, just add a line like this:

exten => s,1,Hangup

And leave everything else in that context unchanged.

Cheers
Tony
-- 
Tony Mountifield
Work: t...@softins.co.uk - http://www.softins.co.uk
Play: t...@mountifield.org - http://tony.mountifield.org

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

Check out the new Asterisk community forum at: https://community.asterisk.org/

New to Asterisk? Start here:
  https://wiki.asterisk.org/wiki/display/AST/Getting+Started

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users