package/asterisk: security bump to version 16.21.1
PATCH 1/1 package/asterisk: security bump to version 16.21.1
Fixes the following security issues:
16.15.0:
- ASTERISK-29057: pjsip: Crash on call rejection during high load
16.15.1:
- AST-2020-003: Remote crash in res_pjsip_diversion
A crash can occur in Asterisk when a SIP message is received that has a History-Info header, which contains a tel-uri.
https://downloads.asterisk.org/pub/security/AST-2020-003.pdf
- AST-2020-004: Remote crash in res_pjsip_diversion
A crash can occur in Asterisk when a SIP 181 response is received that has a Diversion header, which contains a tel-uri.
https://downloads.asterisk.org/pub/security/AST-2020-004.pdf
16.16.0:
- ASTERISK-29219: res_pjsip_diversion: Crash if Tel URI contains History-Info
16.16.1:
- AST-2021-001: Remote crash in res_pjsip_diversion
If a registered user is tricked into dialing a malicious number that sends lots of 181 responses to Asterisk, each one will cause a 181 to be sent back to the original caller with an increasing number of entries in the “Supported” header. Eventually the number of entries in the header exceeds the size of the entry array and causes a crash.
https://downloads.asterisk.org/pub/security/AST-2021-001.pdf
- AST-2021-002: Remote crash possible when negotiating T.38 When re-negotiating for T.38 if the initial remote response was delayed just enough Asterisk would send both audio and T.38 in the SDP. If this happened, and the remote responded with a declined T.38 stream then Asterisk would crash.
https://downloads.asterisk.org/pub/security/AST-2021-002.pdf
- AST-2021-003: Remote attacker could prematurely tear down SRTP calls An unauthenticated remote attacker could replay SRTP packets which could cause an Asterisk instance configured without strict RTP validation to tear down calls prematurely.
https://downloads.asterisk.org/pub/security/AST-2021-003.pdf
- AST-2021-004: An unsuspecting user could crash Asterisk with multiple hold/unhold requests
Due to a signedness comparison mismatch, an authenticated WebRTC client could cause a stack overflow and Asterisk crash by sending multiple hold/unhold requests in quick succession.
https://downloads.asterisk.org/pub/security/AST-2021-004.pdf
- AST-2021-005: Remote Crash Vulnerability in PJSIP channel driver Given a scenario where an outgoing call is placed from Asterisk to a remote SIP server it is possible for a crash to occur.
https://downloads.asterisk.org/pub/security/AST-2021-005.pdf
16.16.2:
- AST-2021-006: Crash when negotiating T.38 with a zero port When Asterisk sends a re-invite initiating T.38 faxing and the endpoint responds with a m=image line and zero port, a crash will occur in Asterisk.
This is a reoccurrence of AST-2019-004.
https://downloads.asterisk.org/pub/security/AST-2021-006.pdf
16.17.0:
- ASTERISK-29203 / AST-2021-002 — Another scenario is causing a crash
- ASTERISK-29260: sRTP Replay Protection ignored; even tears down long calls
- ASTERISK-29227: res_pjsip_diversion: sending multiple 181 responses causes memory corruption and crash
16.19.1:
- AST-2021-007: Remote Crash Vulnerability in PJSIP channel driver When Asterisk receives a re-INVITE without SDP after having sent a BYE request a crash will occur. This occurs due to the Asterisk channel no longer being present while code assumes it is.
https://downloads.asterisk.org/pub/security/AST-2021-007.pdf
- AST-2021-008: Remote crash when using IAX2 channel driver
If the IAX2 channel driver receives a packet that contains an unsupported media format it can cause a crash to occur in Asterisk.
https://downloads.asterisk.org/pub/security/AST-2021-008.pdf
- AST-2021-009: pjproject/pjsip: crash when SSL socket destroyed during handshake
Depending on the timing, it’s possible for Asterisk to crash when using a TLS connection if the underlying socket parent/listener gets destroyed during the handshake.
https://downloads.asterisk.org/pub/security/AST-2021-009.pdf
16.20.0:
- ASTERISK-29415: Crash in PJSIP TLS transport
- ASTERISK-29381: chan_pjsip: Remote denial of service by an authenticated user
In addition, a large number of bugfixes.
Drop now upstreamed 0006-AC_HEADER_STDC-causes-a-compile-failure-with-autoconf-2-70.patch.
--- ...a-compile-failure-with-autoconf-2-70.patch | 171 ------------------ package/asterisk/asterisk.hash | 2 +- package/asterisk/asterisk.mk | 2 +- 3 files changed, 2 insertions(+), 173 deletions(-) delete mode 100644 package/asterisk/0006-AC_HEADER_STDC-causes-a-compile-failure-with-autoconf-2-70.patch
package/asterisk/0006-AC_HEADER_STDC-causes-a-compile-failure-with-autoconf-2-70.patch deleted +0 -171
@@ -1,171 +0,0 @@ -From 060ce10163e46a740c15036fc56214468abc710b Mon Sep 17 00:00:00 2001 -From: Jaco Kroon <[email protected]> -Date: Fri, 8 Jan 2021 18:02:47 +0200 -Subject: [PATCH] AC_HEADER_STDC causes a compile failure with autoconf 2.70 - -From https://www.mail-archive.com/[email protected]/msg04408.html - -> ... the long-obsolete AC_HEADER_STDC, previously used internally by -> AC_INCLUDES_DEFAULT, used AC_EGREP_HEADER. The AC_HEADER_STDC macro -> is now a no-op (and is not used at all within Autoconf anymore), so -> that change is likely what made the first use of AC_EGREP_HEADER the -> one inside the if condition, causing the observed results. - -The implication is that the test does nothing anyway, and due to it -being a no-op from 2.70 onwards, results in the required not being set -to yes, resulting in ./configure to fail. - -Change-Id: Ic1ff38d87f791fbf1f2a80512f81bb7110392460 -Signed-off-by: Jaco Kroon <[email protected]> - -[Retrieved from: -https://github.com/asterisk/asterisk/commit/060ce10163e46a740c15036fc56214468abc710b] -Signed-off-by: Fabrice Fontaine <[email protected]> ---- - configure | 116 --------------------------------------------------- - configure.ac | 5 --- - 2 files changed, 121 deletions(-) - -diff --git a/configure b/configure -index 3594ac62f0c..735a8e98c7f 100755 ---- a/configure -+++ b/configure -@@ -13129,122 +13129,6 @@ if test -z $ac_header_dirent -o "$ac_header_dirent" = "no"; then - as_fn_error $? "*** Could not find dirent header that defines 'DIR'." "$LINENO" 5 - fi - --{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for ANSI C header files" >&5 --$as_echo_n "checking for ANSI C header files... " >&6; } --if ${ac_cv_header_stdc+:} false; then : -- $as_echo_n "(cached) " >&6 --else -- cat confdefs.h - <<_ACEOF >conftest.$ac_ext --/* end confdefs.h. */ --#include <stdlib.h> --#include <stdarg.h> --#include <string.h> --#include <float.h> -- --int --main () --{ -- -- ; -- return 0; --} --_ACEOF --if ac_fn_c_try_compile "$LINENO"; then : -- ac_cv_header_stdc=yes --else -- ac_cv_header_stdc=no --fi --rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -- --if test $ac_cv_header_stdc = yes; then -- # SunOS 4.x string.h does not declare mem*, contrary to ANSI. -- cat confdefs.h - <<_ACEOF >conftest.$ac_ext --/* end confdefs.h. */ --#include <string.h> -- --_ACEOF --if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | -- $EGREP "memchr" >/dev/null 2>&1; then : -- --else -- ac_cv_header_stdc=no --fi --rm -f conftest* -- --fi -- --if test $ac_cv_header_stdc = yes; then -- # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI. -- cat confdefs.h - <<_ACEOF >conftest.$ac_ext --/* end confdefs.h. */ --#include <stdlib.h> -- --_ACEOF --if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | -- $EGREP "free" >/dev/null 2>&1; then : -- --else -- ac_cv_header_stdc=no --fi --rm -f conftest* -- --fi -- --if test $ac_cv_header_stdc = yes; then -- # /bin/cc in Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi. -- if test "$cross_compiling" = yes; then : -- : --else -- cat confdefs.h - <<_ACEOF >conftest.$ac_ext --/* end confdefs.h. */ --#include <ctype.h> --#include <stdlib.h> --#if ((' ' & 0x0FF) == 0x020) --# define ISLOWER(c) ('a' <= (c) && (c) <= 'z') --# define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c)) --#else --# define ISLOWER(c) \ -- (('a' <= (c) && (c) <= 'i') \ -- || ('j' <= (c) && (c) <= 'r') \ -- || ('s' <= (c) && (c) <= 'z')) --# define TOUPPER(c) (ISLOWER(c) ? ((c) | 0x40) : (c)) --#endif -- --#define XOR(e, f) (((e) && !(f)) || (!(e) && (f))) --int --main () --{ -- int i; -- for (i = 0; i < 256; i++) -- if (XOR (islower (i), ISLOWER (i)) -- || toupper (i) != TOUPPER (i)) -- return 2; -- return 0; --} --_ACEOF --if ac_fn_c_try_run "$LINENO"; then : -- --else -- ac_cv_header_stdc=no --fi --rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \ -- conftest.$ac_objext conftest.beam conftest.$ac_ext --fi -- --fi --fi --{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_header_stdc" >&5 --$as_echo "$ac_cv_header_stdc" >&6; } --if test $ac_cv_header_stdc = yes; then -- --$as_echo "#define STDC_HEADERS 1" >>confdefs.h -- --fi -- --if test "$ac_cv_header_stdc" != "yes"; then -- as_fn_error $? "*** ANSI C header files not found." "$LINENO" 5 --fi -- - { $as_echo "$as_me:${as_lineno-$LINENO}: checking for sys/wait.h that is POSIX.1 compatible" >&5 - $as_echo_n "checking for sys/wait.h that is POSIX.1 compatible... " >&6; } - if ${ac_cv_header_sys_wait_h+:} false; then : -diff --git a/configure.ac b/configure.ac -index 9ae3769d02e..2260fe63268 100644 ---- a/configure.ac -+++ b/configure.ac -@@ -616,11 +616,6 @@ if test -z $ac_header_dirent -o "$ac_header_dirent" = "no"; then - AC_MSG_ERROR([*** Could not find dirent header that defines 'DIR'.]) - fi - --AC_HEADER_STDC --if test "$ac_cv_header_stdc" != "yes"; then -- AC_MSG_ERROR([*** ANSI C header files not found.]) --fi -- - AC_HEADER_SYS_WAIT - if test "$ac_cv_header_sys_wait_h" != "yes"; then - AC_MSG_ERROR([*** POSIX.1 compatible sys/wait.h is required.])
package/asterisk/asterisk.hash +1 -1
@@ -1,5 +1,5 @@ # Locally computed -sha256 226eaef400d2d335ce29d7b3c8aca8dfdfc5e854c215e0c47615c095ced12171 asterisk-16.14.1.tar.gz +sha256 1ba86666072b903e24b5cfef3d6d607d0d090c0fd232429ed410496e8f93ac40 asterisk-16.21.1.tar.gz # sha1 from: http://downloads.asterisk.org/pub/telephony/sounds/releases # sha256 locally computed
package/asterisk/asterisk.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -ASTERISK_VERSION = 16.14.1 +ASTERISK_VERSION = 16.21.1 # Use the github mirror: it's an official mirror maintained by Digium, and # provides tarballs, which the main Asterisk git tree (behind Gerrit) does not. ASTERISK_SITE = $(call github,asterisk,asterisk,$(ASTERISK_VERSION))
Signature · 6 lines
2.20.1 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Hello Peter,
Quoted 1 line · On Thu, 21 Oct 2021 08:40:28 +0200 Peter Korsgaard <[email protected]> wrote:
Fixes the following security issues:
I have applied to master, but what's quite worrying is that there were 0 CVEs affecting asterisk in version 16.14.1 according to
http://autobuild.buildroot.net/stats/master.html. Does this mean that the Asterisk community is not submitting CVEs for their security vulnerabilities ?
Thomas
Signature · 7 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 6 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Hello Peter,
On Thu, 21 Oct 2021 08:40:28 +0200
Peter Korsgaard <[email protected]> wrote:
Quoted 7 lines
Quoted 1 line
Fixes the following security issues:
I have applied to master, but what's quite worrying is that there were 0 CVEs affecting asterisk in version 16.14.1 according to
http://autobuild.buildroot.net/stats/master.html. Does this mean that the Asterisk community is not submitting CVEs for their security vulnerabilities ?
Looks like it. I also didn't find any CVE references in the description of the issues I listed :/
Signature · 5 lines
Bye, Peter Korsgaard _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Korsgaard <[email protected]> writes:
Hi,
Quoted 10 lines
Quoted 7 lines
Quoted 1 line
Fixes the following security issues:
I have applied to master, but what's quite worrying is that there were 0 CVEs affecting asterisk in version 16.14.1 according to
http://autobuild.buildroot.net/stats/master.html. Does this mean that the Asterisk community is not submitting CVEs for their security vulnerabilities ?Looks like it. I also didn't find any CVE references in the description of the issues I listed :/
Looking closer, there are in fact CVEs for some of the issues, E.G.:
https://downloads.asterisk.org/pub/security/AST-2021-001.html
But that refers to a digium:asterisk CPE rather than the asterisk:open_source one we look for.
Looking at the CPE database, we should probably use that CPE identifier instead as it looks much more actively used (1154 entries vs 61):
Fabrice, you added the CPE variables for asterisk. Any specific reason to use asterisk/open_source?
Signature · 5 lines
Bye, Peter Korsgaard _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Hi,
Quoted 26 lines · Peter Korsgaard
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
"Peter" == Peter Korsgaard <[email protected]> writes:
Hi,
Quoted 10 lines
Quoted 7 lines
Quoted 1 line
Fixes the following security issues:
I have applied to master, but what's quite worrying is that there were 0 CVEs affecting asterisk in version 16.14.1 according to
http://autobuild.buildroot.net/stats/master.html. Does this mean that the Asterisk community is not submitting CVEs for their security vulnerabilities ?Looks like it. I also didn't find any CVE references in the description of the issues I listed :/
Looking closer, there are in fact CVEs for some of the issues, E.G.:
https://downloads.asterisk.org/pub/security/AST-2021-001.html
But that refers to a digium:asterisk CPE rather than the asterisk:open_source one we look for.
Looking at the CPE database, we should probably use that CPE identifier instead as it looks much more actively used (1154 entries vs 61):
Quoted 6 lines
Fabrice, you added the CPE variables for asterisk. Any specific reason to use asterisk/open_source?
No specific reason, I missed that the digium entry was more up to date.
Quoted 3 lines
--
Bye, Peter Korsgaard
Best Regards,
Fabrice
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 1 line · On Sun, 24 Oct 2021 23:10:51 +0200 Fabrice Fontaine…
No specific reason, I missed that the digium entry was more up to date.
Ideally, we should notify the NVD people that they seem to have two different CPE identifiers for the same software product.
Best regards,
Thomas
Signature · 7 lines
Thomas Petazzoni, co-owner and CEO, Bootlin Embedded Linux and Kernel engineering and training https://bootlin.com _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
All,
Quoted 9 lines
From: buildroot <[email protected]> on behalf of Thomas Petazzoni <[email protected]>
Sent: Monday, October 25, 2021 2:20 AM
To: Fabrice Fontaine <[email protected]>
Cc: Weber, Matthew L Collins <[email protected]>; Yann E. MORIN <[email protected]>; Buildroot Mailing List <[email protected]>
Subject: [External] Re: [Buildroot] [PATCH] package/asterisk: security bump to version 16.21.1
On Sun, 24 Oct 2021 23:10:51 +0200
Fabrice Fontaine <[email protected]> wrote:
Quoted 5 lines
Quoted 1 line
No specific reason, I missed that the digium entry was more up to date.
Ideally, we should notify the NVD people that they seem to have two different CPE identifiers for the same software product.
I've sent an email, and CC'd you guys. From what I can tell, the business CPE had been used for a long time, and recently they split it out into a few different CPE. Honestly, not deprecating the old one and going cleanly to the new one seems like an opportunity for CVE not to get assigned correctly. I do think we should use the open-source CPE and see if that covers our Asterisk version. Then we could compare the CVE between the old/new for that version and the more recent. That comparison could lead to sending in CVE updates for any CVE->"both CPEs" mapping updates.
-Matt
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 95 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Korsgaard <[email protected]> writes:
Fixes the following security issues:
16.15.0:
- ASTERISK-29057: pjsip: Crash on call rejection during high load16.15.1:
- AST-2020-003: Remote crash inres_pjsip_diversion
A crash can occur in Asterisk when a SIP message is received that has a History-Info header, which contains a tel-uri.
https://downloads.asterisk.org/pub/security/AST-2020-003.pdf- AST-2020-004: Remote crash in
res_pjsip_diversion
A crash can occur in Asterisk when a SIP 181 response is received that has a Diversion header, which contains a tel-uri.
https://downloads.asterisk.org/pub/security/AST-2020-004.pdf16.16.0:
- ASTERISK-29219:res_pjsip_diversion: Crash if Tel URI contains History-Info16.16.1:
- AST-2021-001: Remote crash inres_pjsip_diversion
If a registered user is tricked into dialing a malicious number that sends lots of 181 responses to Asterisk, each one will cause a 181 to be sent back to the original caller with an increasing number of entries in the “Supported” header. Eventually the number of entries in the header exceeds the size of the entry array and causes a crash.
https://downloads.asterisk.org/pub/security/AST-2021-001.pdf- AST-2021-002: Remote crash possible when negotiating T.38 When re-negotiating for T.38 if the initial remote response was delayed just enough Asterisk would send both audio and T.38 in the SDP. If this happened, and the remote responded with a declined T.38 stream then Asterisk would crash.
https://downloads.asterisk.org/pub/security/AST-2021-002.pdf- AST-2021-003: Remote attacker could prematurely tear down SRTP calls An unauthenticated remote attacker could replay SRTP packets which could cause an Asterisk instance configured without strict RTP validation to tear down calls prematurely.
https://downloads.asterisk.org/pub/security/AST-2021-003.pdf- AST-2021-004: An unsuspecting user could crash Asterisk with multiple hold/unhold requests
Due to a signedness comparison mismatch, an authenticated WebRTC client could cause a stack overflow and Asterisk crash by sending multiple hold/unhold requests in quick succession.
https://downloads.asterisk.org/pub/security/AST-2021-004.pdf- AST-2021-005: Remote Crash Vulnerability in PJSIP channel driver Given a scenario where an outgoing call is placed from Asterisk to a remote SIP server it is possible for a crash to occur.
https://downloads.asterisk.org/pub/security/AST-2021-005.pdf16.16.2:
- AST-2021-006: Crash when negotiating T.38 with a zero port When Asterisk sends a re-invite initiating T.38 faxing and the endpoint responds with a m=image line and zero port, a crash will occur in Asterisk.
This is a reoccurrence of AST-2019-004.
https://downloads.asterisk.org/pub/security/AST-2021-006.pdf16.17.0:
- ASTERISK-29203 / AST-2021-002 — Another scenario is causing a crash- ASTERISK-29260: sRTP Replay Protection ignored; even tears down long calls
- ASTERISK-29227:
res_pjsip_diversion: sending multiple 181 responses causes memory corruption and crash16.19.1:
- AST-2021-007: Remote Crash Vulnerability in PJSIP channel driver When Asterisk receives a re-INVITE without SDP after having sent a BYE request a crash will occur. This occurs due to the Asterisk channel no longer being present while code assumes it is.
https://downloads.asterisk.org/pub/security/AST-2021-007.pdf- AST-2021-008: Remote crash when using IAX2 channel driver
If the IAX2 channel driver receives a packet that contains an unsupported media format it can cause a crash to occur in Asterisk.
https://downloads.asterisk.org/pub/security/AST-2021-008.pdf- AST-2021-009: pjproject/pjsip: crash when SSL socket destroyed during handshake
Depending on the timing, it’s possible for Asterisk to crash when using a TLS connection if the underlying socket parent/listener gets destroyed during the handshake.
https://downloads.asterisk.org/pub/security/AST-2021-009.pdf16.20.0:
- ASTERISK-29415: Crash in PJSIP TLS transport- ASTERISK-29381:
chan_pjsip: Remote denial of service by an authenticated user
Quoted 6 lines
In addition, a large number of bugfixes.
Drop now upstreamed 0006-AC_HEADER_STDC-causes-a-compile-failure-with-autoconf-2-70.patch.
Signed-off-by Peter Korsgaard <[email protected]>
Committed to 2021.02.x and 2021.08.x, thanks.
Signature · 5 lines
Bye, Peter Korsgaard _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot