Community |
Community.Security-Audit HistoryHide minor edits - Show changes to markup April 28, 2022, at 06:00 PM
by
- Changed lines 7-8 from:
The Security Audit is completed! [[ https://blog.opensips.org/2022/04/28/opensips-security-audit-facts-and-results/|A lot of fuzzing, testing and of course fixing]]. Everything just to make OpenSIPS more secure. to:
The Security Audit is completed! A lot of fuzzing, testing and of course fixing. Everything just to make OpenSIPS more secure. April 28, 2022, at 06:00 PM
by
- Changed lines 7-8 from:
The fund raising is completed, thanks to the generous contributions we received from all over our community!!! Now it is to start the audit process, updates will follow here. to:
The Security Audit is completed! [[ https://blog.opensips.org/2022/04/28/opensips-security-audit-facts-and-results/|A lot of fuzzing, testing and of course fixing]]. Everything just to make OpenSIPS more secure. September 22, 2021, at 02:31 PM
by
- Added lines 4-13:
September 14, 2021, at 09:33 AM
by
- Changed line 91 from:
to:
September 14, 2021, at 08:54 AM
by
- Changed line 47 from:
Collected amount at 9th of Sept 2021 : $27,220\\ to:
Collected amount at 13th of Sept 2021 : $27,220\\ September 14, 2021, at 08:53 AM
by
- Changed lines 47-49 from:
Collected amount at 9th of Sept 2021 : $26,020 to:
Collected amount at 9th of Sept 2021 : $27,220 Added line 91:
September 10, 2021, at 04:23 PM
by
- Changed lines 47-49 from:
Collected amount at 9th of Sept 2021 : $24,660 to:
Collected amount at 9th of Sept 2021 : $26,020 Changed line 90 from:
to:
September 09, 2021, at 03:53 PM
by
- Changed line 84 from:
to:
Changed line 87 from:
to:
September 09, 2021, at 03:50 PM
by
- Changed lines 47-49 from:
Collected amount at 9th of Sept 2021 : $23,660 to:
Collected amount at 9th of Sept 2021 : $24,660 Added line 83:
September 09, 2021, at 03:49 PM
by
- Changed lines 47-49 from:
Collected amount at 7th of Sept 2021 : $22,640 to:
Collected amount at 9th of Sept 2021 : $23,660 Changed lines 83-89 from:
to:
September 08, 2021, at 08:04 PM
by
- Changed lines 47-49 from:
Collected amount at 7th of Sept 2021 : $20,640 to:
Collected amount at 7th of Sept 2021 : $22,640 Added lines 82-83:
September 08, 2021, at 07:51 PM
by
- Changed lines 47-49 from:
Collected amount at 7th of Sept 2021 : $20,390 to:
Collected amount at 7th of Sept 2021 : $20,640 Added lines 80-81:
September 08, 2021, at 07:25 PM
by
- Changed lines 47-49 from:
Collected amount at 7th of Sept 2021 : $19,390 to:
Collected amount at 7th of Sept 2021 : $20,390 Added line 79:
September 07, 2021, at 06:19 PM
by
- Changed lines 47-49 from:
Collected amount at 7th of Sept 2021 : $18,890 to:
Collected amount at 7th of Sept 2021 : $19,390 Changed lines 76-77 from:
to:
September 07, 2021, at 12:13 PM
by
- Changed lines 47-49 from:
Collected amount at 22nd of July 2021 : $17,790 to:
Collected amount at 7th of Sept 2021 : $18,890 Added lines 76-77:
July 27, 2021, at 10:32 AM
by
- Changed lines 47-49 from:
Collected amount at 22nd of July 2021 : $13,290 to:
Collected amount at 22nd of July 2021 : $17,790 Added line 75:
July 23, 2021, at 03:57 PM
by
- Changed lines 47-48 from:
Collected amount at 17th of July 2021 : $11,890 to:
Collected amount at 22nd of July 2021 : $13,290 July 23, 2021, at 03:56 PM
by
- Added lines 73-74:
July 19, 2021, at 03:10 PM
by
- Changed lines 47-49 from:
Collected amount at 4th of July 2021 : $11,690 to:
Collected amount at 17th of July 2021 : $11,890 Added lines 71-72:
July 06, 2021, at 09:30 AM
by
- Changed lines 47-49 from:
Collected amount at 4th of July 2021 : $11,540 to:
Collected amount at 4th of July 2021 : $11,690 Added line 70:
July 05, 2021, at 09:36 AM
by
- Changed lines 47-49 from:
Collected amount at 1st of July 2021 : $9,540 to:
Collected amount at 4th of July 2021 : $11,540 Added line 69:
July 01, 2021, at 05:34 PM
by
- Changed line 47 from:
Collected amount at 28th of June 2021 : $9,540\\ to:
Collected amount at 1st of July 2021 : $9,540\\ July 01, 2021, at 05:33 PM
by
- Changed lines 47-49 from:
Collected amount at 28th of June 2021 : $6,440 to:
Collected amount at 28th of June 2021 : $9,540 Added lines 66-68:
June 28, 2021, at 06:49 PM
by
- Changed line 75 from:
to:
June 28, 2021, at 06:49 PM
by
- Changed line 75 from:
to:
June 28, 2021, at 09:55 AM
by
- Changed lines 47-49 from:
Collected amount at 24th of June 2021 : $6,240 to:
Collected amount at 28th of June 2021 : $6,440 Added line 65:
June 25, 2021, at 10:18 AM
by
- Changed lines 47-49 from:
Collected amount at 24th of June 2021 : $6,140 to:
Collected amount at 24th of June 2021 : $6,240 Changed line 57 from:
to:
Added line 64:
June 25, 2021, at 08:54 AM
by
- Deleted lines 48-49:
(:progress 6140/24000:) June 25, 2021, at 08:53 AM
by
- Added line 50:
(:progress 6140/24000:) June 25, 2021, at 08:45 AM
by
- Changed lines 47-50 from:
Collected amount at 24th of June 2021 : $2,820 to:
Collected amount at 24th of June 2021 : $6,140 Added line 55:
Added lines 61-64:
June 24, 2021, at 03:21 PM
by
- Changed lines 47-50 from:
Collected amount at 24th of June 2021 : $2,620 to:
Collected amount at 24th of June 2021 : $2,820 Added lines 58-59:
June 24, 2021, at 12:42 PM
by
- Changed lines 47-50 from:
Collected amount at 24th of June 2021 : $0 to:
Collected amount at 24th of June 2021 : $2,620 Changed lines 52-53 from:
to:
June 24, 2021, at 11:08 AM
by
- Changed lines 5-6 from:
The Audit is an Open project - the results will be public and the all the derived fixes and enhancements will be of the benefit of the entire community- they will go into the public project/code. Nevertheless, the success of this endeavor highly depends on the support and sponsoring of the community. to:
The Audit is an Open project - the results will be public and the all the derived fixes and enhancements will be of the benefit of the entire community- they will go into the public project/code. June 24, 2021, at 11:07 AM
by
- Changed line 5 from:
The Audit is an Open project - the results will be public and the all the derived fixes and enhancements will be of the benefit of the entire community- they will go into the public project/code. to:
The Audit is an Open project - the results will be public and the all the derived fixes and enhancements will be of the benefit of the entire community- they will go into the public project/code. Nevertheless, the success of this endeavor highly depends on the support and sponsoring of the community. June 24, 2021, at 11:02 AM
by
- Added lines 7-11:
(:table border=0 cellpadding=5 cellspacing=0 width=100% :) (:cell width=70%:) Added lines 44-56:
The current statusCollected amount at 24th of June 2021 : $0 Our Sponsors: (:cell width=30%:) Changed lines 69-79 from:
The current statusCollected amount at 24th of June 2021 : $0 Our Sponsors: to:
(:tableend:) June 24, 2021, at 10:48 AM
by
- Changed line 50 from:
For any other information, please do not hesitate to contact us? ! to:
For any other information, please do not hesitate to contact us ! Changed lines 54-56 from:
Collected amount at 24th of June 2021 : $0 Remaining to collect : $24,000 to:
Collected amount at 24th of June 2021 : $0 Added line 60:
June 24, 2021, at 10:46 AM
by
- Added lines 1-62:
Community -> The Security AuditFollowing the OpenSIPS 3.2 major release (LTS), based on the community feedback, the decision of performing a professional security audit was taken. This security audit is based on the concept of White box Penetration Testing and it will be managed at the project level, with the help of community, for the benefits of the community. The Audit is an Open project - the results will be public and the all the derived fixes and enhancements will be of the benefit of the entire community- they will go into the public project/code. Why a security auditOpenSIPS 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 auditThe 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 doneThe 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. Get involved by sponsoringAs said, this is a community effort, for the community's benefit. So, please be part of this effort and sponsor this Security Audit work. There are multiple ways of doing that:
All our sponsors, tiny or generous, will be publicly listed here, as a sign of gratitude for their contribution. For any other information, please do not hesitate to contact us? ! The current statusCollected amount at 24th of June 2021 : $0 Remaining to collect : $24,000 Our Sponsors: Copyright 2021, The OpenSIPS Project |