Reporting security bugs
We support responsible disclosure and we hope that anyone who finds a potential security issue in our ecosystem acts with discretion and forbearance.
What is Considered A Security Issue
This is a general outline and not an exclusive listing of possibilities.
- Issues that affect the availability of one of more services that are part of the Wikimedia ecosystem, but in particular when this is the result of a hostile set of actions or campaign.
- When the integrity of data hosted by the Wikimedia Foundation or affiliated entities is at risk of being corrupted, tampered with, or otherwise modified in an unauthorized manner.
- When the confidentiality of data owned by the Wikimedia Foundation or its affiliated entities is compromised, such that information meant to be restricted or private is leaked, revealed, stolen, or exfiltrated in an unauthorized manner.
Reporting A Security Issue
Such reports will not be publicly visible at the time of reporting. See below for further process once issues are resolved.
What to Include In A Security Issue Report
- Step-by-step instructions to reproduce the issue
- If possible, proof-of-concept code demonstrating the issue is a best practice
- If the vulnerability can be reproduced on a Wikimedia project (such as Wikipedia or Wiktionary) please indicate which as site configurations vary
- If applicable, indicate if you are logged in or logged out when the issue occurs
- For XSS or vulnerabilities that require a specific browser or plugin, please indicate which browser and version you are using. Specific version of any software used will be helpful.
- OWASP vulnerability category (using OWASP Top 10 for 2017), or CWE id (using CWE By Research Concepts)
- CVE if assigned (using the NIST CVE database)
- Any other information needed to investigate and reproduce the issue
Phabricator accounts can be created using an existing SUL Wiki account.
What Happens When Security Issues Are Reported
- Determine whether we consider it to be a security issue
- Attempt to reproduce the issue, and assign a priority to the bug based on its impact.
- A patch will be added in Phabricator, and another person will review it.
- The patch should contain regression tests, whenever possible.
- The patch will be deployed on the Wikimedia cluster, and access to the patch will be given to a few trusted partners and distributors.
- If applicable, the patch will be included in the next release of MediaWiki. If the impact of the vulnerability is especially bad, or we have indication that it is being actively exploited, we will make a special security release of MediaWiki to ensure third parties are protected.
- Unless you explicitly indicate that certain information must not be published, we will make the Phabricator ticket public when the fix is released, and credit you in the release announcement. If you report the issue via email to firstname.lastname@example.org the email itself may be publicly released. This may include your email address and signature unless you request otherwise. The Phabricator tag PermanentlyPrivate will ensure reports are kept confidential in perpetuity.
- Credit will be given to the reporter in the commit message fixing the issue
- Credit will be given to the reporter in the official announcement email going to the MediaWiki-announce mailing lists
- Credit will be given on Wikimedia Security Team/Thanks for vulnerabilities that are in MediaWiki core or a bundled extension [Todo: Clarify process around non-MediaWiki core security bugs]
- Currently there is no budget for security reports. This means no bounties are paid by Wikimedia Foundation for discovering security bugs on these projects, either in money or in merchandise.
- [Proposed, as of right now this does not happen] For Security issues in MediaWiki core or an extension, the reporter will be added to a special "Security Researchers" section of the page Special:Version/credits and the CREDITS text file (in the source code) included with MediaWiki.
Tracking Report Remediation
When possible during the remediation process, the security bugs should have comments that include:
- Step-by-step instructions to reproduce further issues
- Links to the commits that introduced the bug
- Links to the Gerrit changesets that fixes the bug
Reporter access to their own authored reports is standard, but to gain access to security protected issues generally there is a separate process
If you would like to provide a patch for a security bug, please add it as an attachment to the Phabricator task. You can either drag-and-drop the patch into the comment area, or include a diff of the patch as a comment. Please do not add it as a patchset in Gerrit. All Gerrit patchsets (including "drafts") are publicly accessible.
- See wikitech:How to deploy code#Creating a Security Patch for steps to create these patches, and wikitech:How to deploy code#Security patches for how these patches are deployed.
Related Security Content
|Project||Use by Wikimedia Security Team|
|mediawiki.org||General content for Policy, SOPs, etc. Official Security team page.|
|wikitech.wikimedia.org||Procedural or instructional material that is not training.|
|meta.wikimedia.org||Policy and other content for translation.|
|office.wikimedia.org||Sensitive or private content. Must have an NDA and appropriate access.|
|foundation.wikimedia.org||Canonical location for Policy|
Understanding Wikimedia Security Team documentation structure