]> git.ipfire.org Git - thirdparty/asterisk.git/commitdiff
Update for 21.4.3 21.4.3
authorAsterisk Development Team <asteriskteam@digium.com>
Thu, 5 Sep 2024 17:03:28 +0000 (17:03 +0000)
committerAsterisk Development Team <asteriskteam@digium.com>
Thu, 5 Sep 2024 17:03:28 +0000 (17:03 +0000)
.version
CHANGES.md
ChangeLogs/ChangeLog-21.4.3.md [new file with mode: 0644]

index 7bf20f5b8d873e258a619d20321bc5582ad2edef..681355da9ff7548ebd83605fb94feb62b34dd0a1 100644 (file)
--- a/.version
+++ b/.version
@@ -1 +1 @@
-21.4.2
+21.4.3
index 8d167f79af95226499cf32e250db023f870b6793..d2f90c79fa01683ef96cad426dab20eb0484998e 120000 (symlink)
@@ -1 +1 @@
-ChangeLogs/ChangeLog-21.4.2.md
\ No newline at end of file
+ChangeLogs/ChangeLog-21.4.3.md
\ No newline at end of file
diff --git a/ChangeLogs/ChangeLog-21.4.3.md b/ChangeLogs/ChangeLog-21.4.3.md
new file mode 100644 (file)
index 0000000..8ebae31
--- /dev/null
@@ -0,0 +1,63 @@
+
+## Change Log for Release asterisk-21.4.3
+
+### Links:
+
+ - [Full ChangeLog](https://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-21.4.3.md)  
+ - [GitHub Diff](https://github.com/asterisk/asterisk/compare/21.4.2...21.4.3)  
+ - [Tarball](https://downloads.asterisk.org/pub/telephony/asterisk/asterisk-21.4.3.tar.gz)  
+ - [Downloads](https://downloads.asterisk.org/pub/telephony/asterisk)  
+
+### Summary:
+
+- Commits: 1
+- Commit Authors: 1
+- Issues Resolved: 0
+- Security Advisories Resolved: 1
+  - [GHSA-v428-g3cw-7hv9](https://github.com/asterisk/asterisk/security/advisories/GHSA-v428-g3cw-7hv9): A malformed Contact or Record-Route URI in an incoming SIP request can cause Asterisk to crash when res_resolver_unbound is used
+
+### User Notes:
+
+
+### Upgrade Notes:
+
+
+### Commit Authors:
+
+- George Joseph: (1)
+
+## Issue and Commit Detail:
+
+### Closed Issues:
+
+  - !GHSA-v428-g3cw-7hv9: A malformed Contact or Record-Route URI in an incoming SIP request can cause Asterisk to crash when res_resolver_unbound is used
+
+### Commits By Author:
+
+- #### George Joseph (1):
+  - res_resolver_unbound: Test for NULL ub_result in unbound_resolver_callback
+
+
+### Commit List:
+
+-  res_resolver_unbound: Test for NULL ub_result in unbound_resolver_callback
+
+### Commit Details:
+
+#### res_resolver_unbound: Test for NULL ub_result in unbound_resolver_callback
+  Author: George Joseph
+  Date:   2024-08-12
+
+  The ub_result pointer passed to unbound_resolver_callback by
+  libunbound can be NULL if the query was for something malformed
+  like `.1` or `[.1]`.  If it is, we now set a 'ns_r_formerr' result
+  and return instead of crashing with a SEGV.  This causes pjproject
+  to simply cancel the transaction with a "No answer record in the DNS
+  response" error.  The existing "off nominal" unit test was also
+  updated to check this condition.
+
+  Although not necessary for this fix, we also made
+  ast_dns_resolver_completed() tolerant of a NULL result.
+
+  Resolves: GHSA-v428-g3cw-7hv9
+