Contents

• 1 Introduction
• 2 Security announcements
• 3 How do you test Mahara for security issues?
• 4 How do you report a security issue?
• 5 What should you include in your report?
• 6 What will we do?
• 7 What should you keep in mind?
• 8 Security in our development process

Introduction

Security is very important to the Mahara project team. As potential issues are reported to us, we will test, patch if necessary, and release fixes as quickly as possible to the Mahara software for organisations to patch their instances.

The Mahara team 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 if issues are reported to us first via a responsible disclosure.

In particular, we appreciate reports that concern the Mahara software. While potential security issues concerning the Mahara infrastructure and supporting tools can be reported, we rely on the security improvements made by the projects who support and package these tools. For example, if you come across security issues in the wiki that is based on MediaWiki, you may wish to report the issue to the MediaWiki project.

Security announcements

Security announcements for issues in the Mahara software are made in separately to allow community members to subscribe to them and see them easily.

How do you test Mahara for security issues?

We do not approve test accounts on mahara.org and other project infrastructure maintained by the Mahara project team that are created for the purpose of finding security or other issues.

Please install a local copy of Mahara using the latest code on your own infrastructure to test the software. It is open source and you do not incur any fees for installing it.

How do you report a security issue?

You can report security bugs in two different ways:

1. Preferred: Send an email to [email protected]. You will receive an automatic reply acknowledging receipt of your report. We do not include your original message.
2. 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.

Before reporting any potential issues, please verify that

• your report is not covered on our 'Responses to common security reports' page.
• vulnerabilities with the infrastructure haven't already been reported.

We keep a register of all vulnerabilities that have been addressed in the Mahara codebase.

What should you include in your report?

For the Mahara team to investigate security reports, please provide the following information:

• Whether the issue affects the Mahara application (which version was tested?) or a part of the project infrastructure;
• Type of vulnerability and its impact and severity. We recommend determining the CVSS vector string and score;
• Whether the vulnerability has already been published or shared with others;
• Description of the security issue;
• Step-by-step instructions or proof of concept to replicate the issue;
• Was personal information exposed? If so, what happened with it.

What will we do?

Our team will investigate vulnerability reports and be in touch with you within 10 New Zealand business days either with follow-up questions or our assessment and next steps. We appreciate your patience. Some bugs take time to investigate and the process may involve a review of the codebase for similar problems.

If you found a security vulnerability in the Mahara codebase that requires mitigation, we will request a CVE, credit you as reporter in the CVE and on our security contributor page (if you like), and provide a timeline for fixing the problem through publishing a security release for all currently supported versions of Mahara. We aim to address security vulnerabilities as quickly as possible and make fixes available to the Mahara community, allowing organisations to patch their own installations of Mahara. We may prioritise the fixing of issues based on scope and severity of the vulnerability.

We make security release announcements via our official Mahara security advisory forum.

What should you keep in mind?

We ask that you verify that security issues found by automated tools are not false positives. For example, reports of 'possible sensitive information in source code' are unlikely to apply to JavaScript files intentionally downloaded by a web browser and stored in our public source code repository.

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. The Mahara project is unable to request CWE numbers for security issues.

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 our code review guidelines.

Some of the developers are also members of the security team and follow the security guidelines.

NewPP limit report Cached time: 20240813134603 Cache expiry: 86400 Reduced expiry: false Complications: [show‐toc] CPU time usage: 0.008 seconds Real time usage: 0.011 seconds Preprocessor visited node count: 28/1000000 Post‐expand include size: 0/2097152 bytes Template argument size: 0/2097152 bytes Highest expansion depth: 2/100 Expensive parser function count: 0/100 Unstrip recursion depth: 0/20 Unstrip post‐expand size: 0/5000000 bytes Transclusion expansion time report (%,ms,calls,template) 100.00% 0.000 1 -total Saved in parser cache with key maharawikidb-mediawiki-:pcache:idhash:835-0!canonical and timestamp 20240813134603 and revision id 13315.