#### Pre-Submission Checklist
- [*] Commit message has the format required by CONTRIBUTING guide
- [*] Commits are split per component (core, individual modules, libs, utils, ...)
- [*] Each component has a single commit (if not, squash them into one commit)
- [*] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [*] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
- [*] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
I observed this when glancing over commit https://github.com/kamailio/kamailio/commit/f50177003c21f53564be6349c0bb493…
The invalid access is pretty clear, and so is the fix.
Cheers!
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2712
-- Commit Summary --
* domain: fix use after free on domain reload
-- File Changes --
M src/modules/domain/hash.c (3)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2712.patchhttps://github.com/kamailio/kamailio/pull/2712.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/2712
Hello,
a notification to inform about a regression to the AVPs with the integer
IDs that was introduced in the v5.4.5 release when trying to fix an
issue reported from a static code analyzer/fuzzer.
The workaround is to use string names for AVPs, so if you have AVPs like
$avp(i:123), they can be changed to $avp(s:123) in the kamailio.cfg
(ie., replace i: with s: ).
Regression is already fixed in the git branch 5.4, so if you install it
from there, all should be ok. For Debian packages, you can wait till
tomorrow and use the nightly builds of 5.4.x series from the repos
listed at:
* http://deb.kamailio.org/#dev54
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online
May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone)
* https://www.asipto.com/sw/kamailio-advanced-training-online/
I try to refresh the build image for CentOS 6 and can't do it now.
This directory (and version of CentOS) is deprecated. Please see this FAQ
concerning the CentOS release scheme:
https://wiki.centos.org/FAQ/General
Please keep in mind that 6.0, 6.1, 6.2, 6.3, 6.4 , 6.5, 6.6, 6.7, 6.8
, 6.9 and 6.10 no longer get any updates, nor
any security fix's.
The whole CentOS 6 is *dead* and *shouldn't* be used anywhere at *all*
http://mirror.centos.org/centos/6/readme
What our plans about Kamailio releases for RHEL 6 and Cent 6 dists?
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
After upgrading kamailio from 5.4.4 to 5.4.5, the lcr module logs an error for outgoing calls. load_gws returns success (1), but does not populate the avps. Consequently, next_gw fails.
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
kamailio.cfg:
```
loadmodule "lcr.so"
...
modparam("lcr", "db_url", "cluster://cls1")
modparam("lcr", "gw_uri_avp", "$avp(i:709)")
modparam("lcr", "ruri_user_avp", "$avp(i:500)")
modparam("lcr", "tag_avp", "$avp(lcr_tag)")
modparam("lcr", "flags_avp", "$avp(i:712)")
modparam("lcr", "defunct_capability", 1)
modparam("lcr", "lcr_id_avp", "$avp(s:lcr_id_avp)")
modparam("lcr", "defunct_gw_avp", "$avp(s:defunct_gw_avp)")
modparam("lcr", "ping_interval", 60)
...
route[LCR] {
if(!($rU=~"^[+0-9]"))
return;
if(is_method("INVITE")) {
if (!($fU=~"^[+0-9]+$")) {
append_hf("P-Asserted-Identity: <sip:+49xxxxxxxxxxx@xxxxx.de>\n");
append_hf("Privacy: id\n");
$fn = "Anonymous";
$fu = "sip:+49xxxxxxxxxxx@xxxxx.de";
}
if(load_gws(1, $rU, $var(caller_uri)) != 1) {
xlog("L_ERROR", "Couldn't load gateways\n");
sl_send_reply("500", "Server Internal Error - Cannot load gateways");
exit;
} else {
xlog("L_INFO", "GW Selected '$avp(i:709)'\n");
xlog("L_INFO", "Domain of destination: $dd\n");
xlog("L_INFO", "To URI: $tu\n");
}
if(!next_gw()) {
xlog("L_WARN", "No gateway configured for $rU\n");
sl_send_reply("503", "Service not available, no gateways found");
exit;
} else {
xlog("L_INFO", "Calling the first matched gateway\n");
xlog("L_INFO", "ruri_user_avp: '$avp(i:500)'\n");
xlog("L_INFO", "To URI after next_gw: $tu\n");
xlog("L_INFO", "Request URI: $ru\n");
}
t_on_failure("MANAGE_FAILURE_LCR");
route(RELAY);
exit;
}
}
```
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: ERROR: <core> [core/usr_avp.c:152]: create_avp(): 0 ID or NULL NAME AVP!
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: ERROR: <core> [core/usr_avp.c:152]: create_avp(): 0 ID or NULL NAME AVP!
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: INFO: <script>: GW Selected '<null>'
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: INFO: <script>: Domain of destination: <null>
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: INFO: <script>: To URI: sip:+49177xxxxxxx@xx.xxx.x.xxx:5060
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: WARNING: <script>: No gateway configured for +49177xxxxxxx
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
SIP request:
```
INVITE sip:+49177xxxxxxx@xx.xx.xx.xxx:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xx.xx.xxx:xxxxx;branch=z9hG4bK5d833a50
Max-Forwards: 70
From: <sip:+xxxxxxxxxxx@xxx.xx.xx.xxx:xxxxx>;tag=as18ff0d47
To: <sip:+49177xxxxxxx@xx.xx.xx.xxx:5060>
Contact: <sip:+xxxxxxxxxxx@xxx.xx.xx.xxx:xxxxx>
Call-ID: 7489c50703b43b2f03980574181a2f81@xxx.xx.xx.xxx:xxxxx
CSeq: 102 INVITE
User-Agent: Asterisk PBX 13.18.3~dfsg-1ubuntu4
Date: Thu, 15 Apr 2021 21:52:42 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 952
...
```
SIP reply:
```
SIP/2.0 503 Service not available, no gateways found
Via: SIP/2.0/UDP xxx.xx.xx.xxx:xxxxx;branch=z9hG4bK5d833a50;rport=50060;received=xx.xx.xx.xxx
From: <sip:+xxxxxxxxxxx@xxx.xx.xx.xxx:xxxxx>;tag=as18ff0d47
To: <sip:+49177xxxxxxx@xx.xx.xx.xxx:5060>;tag=6a823999ce344a0b461cf8d85d526103.51611a36
Call-ID: 7489c50703b43b2f03980574181a2f81@xxx.xx.xx.xxx:xxxxx
CSeq: 102 INVITE
Server: kamailio (5.4.5 (x86_64/linux))
Content-Length: 0
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
As a workaround, I downgraded to kamailio 5.3.8 because the previous Ubuntu release 5.4.4 is not available anymore at http://deb.kamailio.org/kamailio54/pool/main/k/kamailio/ (why actually?)
### Additional Information
* **Kamailio Version** 5.4.5
* **Operating System**: Ubuntu 18.04
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->
### Root Cause Assumption
https://github.com/kamailio/kamailio/commit/ca1821837dfe7dd6630f628d968ed4d… might be involved in the issue.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2709
I have created a pull request that allows the use of fresh GCC for the
FreeSwitch project.
https://github.com/signalwire/freeswitch/pull/1161
Think we can use the same approach to use fresh GCC for the Kamailio
project.
For RHEL based dist and old Debian dest.
Is it a useful approach to use fresh GCC to build a master branch?
Sergey