Security Disclosure Policy
Matrix.org greatly appreciates investigative work into security vulnerabilities carried out by well-intentioned, ethical security researchers. We follow the practice of responsible disclosure in order to best protect Matrix’s user-base from the impact of security issues. On our side, this means:
- We will respond to security incidents as a priority.
- We will fix the issue as soon as is practical, keeping in mind that not all risks are created equal.
- We will always transparently let the community know about any incident that affects them.
If you have found a security vulnerability in Matrix, we ask that you disclose it responsibly by emailing [email protected]. Optionally, if you want to encrypt your email, you can use our PGP key. Please do not discuss potential vulnerabilities in public without validating with us first.
On receipt the security team will:
- Review the report, verify the vulnerability and respond with confirmation and/or further information requests; we typically reply within 24 hours.
- Once the reported security bug has been addressed we will notify the Researcher, who is then welcome to optionally disclose publicly.
The following is a list of known issues and/or things we do not consider to be an issue. Please do not send reports regarding the following:
- Issues relating to SPF or DMARC.
The Matrix.org Foundation does not ordinarily provide bug bounties, though organisations building on top of Matrix may do so in future.
We maintain a Hall of Fame to recognise those who have responsibly disclosed security issues to us in the past.
Hall of Fame
Reported that Matrix Static (used for view.matrix.org) was vulnerable to XSS via room names due to missing sanitization. Fixed in Matrix Static 0.3.1
Discovered status.matrix.org was running a version of Cachet vulnerable to an SQL injection
. Since this host was used solely for running the status page, we fixed this by decommissioning it and switching to Atlassian's Statuspage service.
Discovered that an explicit assignment of power level 0 was misinterpreted as the default power level. Fixed in Synapse v1.40.0.
Discovered that Element Android was disclosing the filename of end-to-end encrypted attachments to the homeserver. Fixed in Element Android 1.1.8.
IP blacklist bypass via transitional IPv6 addresses on dual-stack networks (CVE-2021-21392
). Fixed in Synapse 1.28.0.
Element iOS crash via an invalid content payload. Fixed in Element iOS 1.1.4.
Denial of service attack via .well-known lookups (CVE-2021-21274
). Fixed in Synapse 1.25.0.
IP blacklist bypass via redirects on some federation and push requests (CVE-2021-21273
). Fixed in Synapse 1.25.0.
HTML injection in login fallback endpoints could be used for a Cross-site-scripting attack (CVE-2020-26891
). Fixed in Synapse 1.21.0.
Misconfigured X-Frame in New Vector internal infrastructure could lead to Clickjacking
An issue where encrypted state events could break incoming call handling. Fixed in Element 1.7.5
An issue where an unexpected language ID in a code block could cause Element to crash. Fixed in Element 1.7.3
Invalid JSON could become part of the room state, acting as a denial of service vector (CVE-2020-26890
). Fixed in Synapse 1.20.0. Disclosed 2020-11-23.
A clickjacking vulnerability in the single-sign-on flow in Synapse. Fixed in Synapse 1.15.2
An issue where replying to a specially formatted message would make it seem like the replier said something they did not. Fixed in Element 1.7.3
A CSRF attack leading to potential unauthorised access to accounts on servers using single-sign-on flows. Fixed as part of matrix-react-sdk#4685
, released in Riot/Web 1.6.3.
A vulnerability in the SAS verification protocol failing to bind the ephemeral public keys. Fixed in MSC2630
, which lists the fixed client versions.
An open redirect vulnerability affecting single sign-on flows. Fixed in Synapse 1.11.1
HTML injection in email invites. A malicious 3rd party invite could inject unescaped HTML into the email template. Fixed in Sydent 1.0.3
SSRF in the URL preview API, which did not blacklist access to 0.0.0.0/32 or ::/128 by default. Fixed in Synapse 0.99.3.1
Insecure pseudo-random number generator in synapse meant that an attacker might be able to predict random values. Fixed in Synapse 0.99.3.1
Insecure pseudo-random number generator in sydent meant that an attacker could predict authentication tokens. Fixed in Sydent 1.0.3
Obsolete and buggy ContentProvider in Riot/Android meant that a malicious local app could compromise account data. Mitigated here
Sydent sesssion ids were predictable, meaning it was possible to infer the total number of validations and also check if an address had been validated. Mitigated here.
Identified a unpatched RCE vulnerability in Matrix.org's public-facing Jenkins. It transpired the vulnerability had been exploited by an attacker
XSS exploit allowing a malicious SWF uploaded to Riot via Firefox to run arbitrary code in the domain of the content repository. Mitigated here.
2018-02-19 - Matrix React SDK - rugk
Origin check of ScalarMessaging postmessage API was insufficient. Mitigated here.
If you think you should be on the list, apologies if we missed you, please mail us at [email protected]