Just to add to what Henning has said… the report is very interesting. I did spot check a few of the examples, as Sandro excellently documented how to reproduce.
The reproduction (such as what you posted with param_parser did not produce the same crash as reported. If you can reproduce something here, please let us know (issue would be best) so it can be handled and documented.
> On Mar 15, 2023, at 3:56 PM, Henning Westerholt <email@example.com
> thanks for sharing this. What was done in the security audit from them is something that was done from many people already done in the past for the Kamailio project. Several people presented about it at different conferences.
> Many modules are also not similar due to the different ways both projects took (e.g., some modules are only present for one of the projects, Kamailio integrated many changes from the SER projects etc..).
> That said, its probably still make sense to review the applicable parts and make sure that it does not affect the current code.
> Sent: Mittwoch, 15. März 2023 20:20
> Subject: [SR-Users] Issues/Vulnerabilities in OpenSipS that may affect Kamailio
> Hi All,
> OpenSipS just released an update to the audit that was done to OpenSips . From my basic coding skills it seems like the changes that were done by the OpenSipS project were not implemented in Kamailio which means that Kamailio is potentially vulnerable? For example you can compare the changes made by OpenSips project here  and the Kamailio code here 
> I am not active much on the list so please don't roast me if I am completely wrong here.
> Kamailio - Users Mailing List - Non Commercial Discussions
> Important: keep the mailing list in the recipients, do not reply only to the sender!
> Edit mailing list options or unsubscribe:
Kamailio - Users Mailing List - Non Commercial Discussions
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe: