Why a security audit

OpenSIPS is one of the most used Open Source SIP Servers, used in thousands of deployments, for various purposes / scenarios. But one factor stands in all these cases - the security of your OpenSIPS, how reliable it is, how vulnerable it is or how robust it is to external attacks or to bogus traffic. These security concerns are very important, in all the OpenSIPS deployment cases, as they exceed the boundary of the operator itself, impacting the end user or the external parties connecting into the operator's OpenSIPS - we all know this when comes to service SLAs.

So far there was an attempt to individually address this security concerns (by private testing), but the effort is high and not shared, so the overall efficiency is rather small. The proper answer is an collective public effort, with public benefits for all.

The goals of this audit

The work aims to uncover critical vulnerabilities within some of the most exposed code in OpenSIPS. Enable Security will be using proven techniques, including instrumented fuzzing, black box fuzzing, manual code review and security testing with their toolset, SIPVicious PRO in a concentrated effort to discover security issues within the project.

The actual work includes development of automated tests, and fuzzing harness code as well as manual testing to identify vulnerabilities such as memory corruption issues, logic issues especially those that may lead to authentication bypass and denial of service vulnerabilities. The identification of such vulnerabilities will allow OpenSIPS to address these bugs which in turn will help the project become an even more robust and secure solution.

Enable Security is known for having dedicated RTC security expertise through its various bug reports, research publications, presentations and other resources that are compiled as part of their contributions to the community and the RTC world. In this case, Enable Security would be focusing on a security audit on OpenSIPS as they do within their commercial security services, thus making a dedicated effort to identify more than just _low hanging fruit_ security issues.

Apart from a technical report with full details of their exploits and methodology, their aim is to provide the community with contributions to the OpenSIPS project so that it can be integrated within the OSS-Fuzz project and other automated quality assurance processes. This will ensure that OpenSIPS can be easily tested for security vulnerabilities that may be introduced in future updates.

How it will be done

The developing team of OpenSIPS worked out together with the Enable Security's team what are the parts of OpenSIPS to be subject to Pen Tests. This decision was taken based on the (1) potential vulnerability of certain parts of the code and (2) the testing / fuzzing possibilities.

We already worked out an commercial agreement with Enable Security for running the Security Audit. And we do appreciate all the help and support from they side, considering the fact that we are a non-commercial Open Source Project.

Based on this agreement, we, as OpenSIPS Project, will have to raise the amount for 24,000 USD. This has to be an collective effort of all the people, companies or other entities which are using OpenSIPS and value the safety and reliability of their OpenSIPS deployments.

Once the amount is fully raise, Enable Security will proceed with performing all the White Box Pen Tests under the commercial agreement. The results of this testing will go public, to the benefits of the entire community.

We, as developers and maintainers of OpenSIPS Project will take on the job of working out the fixes for the potential issues revealed by the testing.

The current status

Collected amount at 13th of Sept 2021 : $27,220
Remaining to collect : -3220$ :)
Our Sponsors: