Security is very important to Mahara developers. As potential issues are reported to us, we will test, patch and release fixes as quickly as possible.
Mahara does not have a bug bounty program. We still appreciate security bug reports and will list their reporters in the Security researchers section of our contributors page as a thank you.
How to test Mahara for security issues
We do not approve test accounts on mahara.org that are created for the purpose of finding security or other issues.
How to report a security issue?
For the Mahara team to investigate security reports, the following information is required from the reporter:
- Description of the security issue including the possible impact if the issue is exploited;
- The severity of the security issue. We recommend determining the CVSS vector string and score;
- Full steps required to allow the project team to verify the security issue;
- Information about how to exploit the security issue;
- Where is the security issue? What hosts or web pages are affected?
- Is the security issue in the Mahara application (which version?) or in the Mahara project infrastructure?
If you want to report a TLS configuration issue, we expect to have an A or A+ rating on SSLLabs. We will only take reports into consideration where our rating would drop below A when caused by TLS configuration issues.
Please note that the Mahara team can only request a CVE for security issues in the Mahara application itself. Also, the Mahara project is unable to request CWE numbers for security issues.
You can report security bugs in two different ways:
- In our bug tracker: If you think (or know) you have found a security bug, please make sure you click "This bug is a security vulnerability" under the "This bug contains information that is" on the bug tracker form.
- You can send and email to firstname.lastname@example.org.
You will receive a response from a Mahara team member acknowledging receipt of your email, typically within 1 or 2 New Zealand business days. If you do not receive a response, please do not assume we're ignoring you. It's quite possible your email didn't make it through a spam filter.
We appreciate your patience. Some bugs take time to correct and the process may involve a review of the codebase for similar problems. Please do not disclose the vulnerability to anyone before the publication of the official Mahara security advisory.
If you report a security vulnerability which was not yet known to the project team, you will be acknowledged on our site and also a resulting bug report. If appropriate, a CVE number is filed and you are credited with the discovery of the vulnerability. The Mahara project does not run a bug bounty and cannot compensate for time spent.
Security in our development process
Mahara developers are committed to achieving the highest standard of security. All commits to the Mahara git repository are reviewed by at least one developer who will enforce the guidelines found in Developer_Area/How_to_Review_Code.
Some of the developers are also members of the security team and follow these guidelines.
Mahara Security Bug Bounty Program (ended)
The Mahara Security Bug Bounty Program ended in October 2012. Please see the announcement for further information.
Responses to common security reports
The Mahara project team receives reports of security vulnerabilities, particularly in the supporting project infrastructure, that after investigation we determine are not valid or do not need to be fixed.