matrix-synapse@1.10.0rc3 vulnerabilities
Homeserver for the Matrix decentralised comms protocol
-
latest version
1.119.0
-
latest non vulnerable version
-
first published
6 years ago
-
latest version published
13 days ago
-
licenses detected
- [0.33.5,1.99.0rc1)
Direct Vulnerabilities
Known vulnerabilities in the matrix-synapse package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to a weakness in how the How to fix Allocation of Resources Without Limits or Throttling? Upgrade |
[,1.105.1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Information Exposure. An attacker can query remote users' device information which can be used to enumerate the remote users known to a homeserver. How to fix Information Exposure? Upgrade |
[,1.95.1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the How to fix Allocation of Resources Without Limits or Throttling? Upgrade |
[,1.94.0rc1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Improper Input Validation due to the improper validation of receipts. An attacker can forge read receipts for any event by knowing the room ID and event ID. How to fix Improper Input Validation? Upgrade |
[0.34.0,1.93.0)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Incorrect Authorization in that it does not check for deactivated status of users during login, under certain conditions. Specifically, JSON Web Tokens must be enabled via the NOTE: Installations configured to only allow login via Single Sign-On (SSO) via CAS, SAML or OpenID Connect (OIDC); or via an external password provider (e.g. LDAP) are not affected. If not using JSON Web Tokens, the list of deactivated users with a password set can be queried from PostgreSQL:
How to fix Incorrect Authorization? Upgrade |
[,1.85.0rc1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) by bypassing the
How to fix Server-side Request Forgery (SSRF)? Upgrade |
[,1.85.0rc1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Denial of Service (DoS) to specific hosts by sending malicious invites. A malicious homeserver can disable its outbound federation to a different homeserver by sending a very large NOTE: Synapse instances with federation disabled are not affected. How to fix Denial of Service (DoS)? Upgrade |
[,1.74.0rc1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Access Restriction Bypass due to Synapse homeservers answering a query for authorisation events not sufficiently checking that the requesting server should be able to access them. Authorisation events include power level events (the list of user IDs and their power levels at the time) and relevant membership events (including the display name of the sender of that event), as well as events like NOTE: This issue is only exploitable when an attacker knows the ID of a target room and the ID of an event from that room, which increases the complexity of a realistic attack. Additionally, this issue is of negligible consequence for public rooms given that any server can easily join the roomand view authorisation events. Deployments in a closed federation where all homeservers are trustworthy are not affected. How to fix Access Restriction Bypass? Upgrade |
[,1.69.0rc1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling such that connections will only be terminated after How to fix Allocation of Resources Without Limits or Throttling? Upgrade |
[,1.53.0)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Denial of Service (DoS) due to incorrect application of event authorization rules. How to fix Denial of Service (DoS)? Upgrade |
[,1.62.0)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Uncontrolled Recursion via the web page preview feature, due to unbounded recursion that can lead to exhaustion of the available stack space for the Synapse process. A malicious user on the home server, or remote users sending URLs that a local user's client can automatically request a URL preview for. Note:
How to fix Uncontrolled Recursion? Upgrade |
[,1.61.1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Directory Traversal. Synapse instances with the media repository enabled can be tricked into downloading a file from a remote server into an arbitrary directory, potentially outside the media store directory. NoteHomeservers with the media repository disabled are unaffected. Homeservers configured with a federation whitelist are also unaffected. How to fix Directory Traversal? Upgrade |
[,1.47.1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Information Exposure. Unauthorised users can access the name, avatar, topic and number of members of a room if they know the ID of the room. This vulnerability is limited to homeservers where:
By default, only homeserver administrators can create groups. However, homeserver administrators can already access this information in the database or using the admin API. As a result, only homeservers where the configuration setting How to fix Information Exposure? Upgrade |
[,1.41.1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Information Exposure. Unauthorised users can access the membership (list of members, with their display names) of a room if they know the ID of the room. The vulnerability is limited to rooms with How to fix Information Exposure? Upgrade |
[,1.41.1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Denial of Service (DoS). Lack of input validation of some parameters on the endpoints used to confirm third-party identifiers could lead to denial of service due to excessive use of disk space and memory. How to fix Denial of Service (DoS)? Upgrade |
[,1.33.0)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Denial of Service (DoS). "Push rules" can specify conditions under which they will match, including Certain patterns can cause very poor performance in the matching engine, leading to a denial-of-service when processing moderate length events. How to fix Denial of Service (DoS)? Upgrade |
[,1.33.2)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Denial of Service (DoS). It is missing input validation of some parameters on the endpoints used to confirm third-party identifiers. This can cause excessive use of disk space and memory leading to resource exhaustion. Note that the How to fix Denial of Service (DoS)? Upgrade |
[,1.28.0)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Open Redirect. Requests to user provided domains are not restricted to external IP addresses when transitional IPv6 addresses are used. Outbound requests to federation, identity servers, when calculating the key validity for third-party invite events, sending push notifications, and generating URL previews are affected. This can cause How to fix Open Redirect? Upgrade |
[,1.28.0)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Denial of Service (DoS). How to fix Denial of Service (DoS)? Upgrade |
[,1.28.0)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the password reset endpoint. The impact depends on the configuration of the domain that Synapse is deployed on, but may allow access to cookies and other browser data, CSRF vulnerabilities, and access to other resources served on the same domain or parent domains. How to fix Cross-site Scripting (XSS)? Upgrade |
[,1.27.0)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Improper Input Validation. HTML injection is possible in notification emails regarding missed messages or expiring account. In the case of notifications for missed messages, an attacker can inject forged content into the email. However, the account expiry feature is not enabled by default and the HTML injection is not controllable by an attacker. How to fix Improper Input Validation? Upgrade |
[,1.27.0)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Insecure Defaults. Requests to user provided domains are not restricted to external IP addresses when calculating the key validity for third-party invite events and sending push notifications. This could cause Synapse to make requests to internal infrastructure. The type of request was not controlled by the user, although limited modification of request bodies was possible. How to fix Insecure Defaults? Upgrade |
[,1.25.0)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Denial of Service (DoS). A malicious homeserver could redirect requests to their How to fix Denial of Service (DoS)? Upgrade |
[0.99.0,1.25.0rc1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Denial of Service (DoS). A malicious or poorly-implemented homeserver can inject malformed events into a room by specifying a different room id in the path of a How to fix Denial of Service (DoS)? Upgrade |
[,1.23.1)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Denial of Service (DoS). It permits non-standard NaN, Infinity, and Infinity JSON values in fields of How to fix Denial of Service (DoS)? Upgrade |
[,1.20.0)
|
matrix-synapse is an ecosystem for open federated Instant Messaging and VoIP. Affected versions of this package are vulnerable to Cross-site Scripting (XSS). Depending on the configuration of the domain that Synapse is deployed on it may allow access to cookies and other browser data, CSRF vulnerabilities, and access to other resources served on the same domain or parent domains. How to fix Cross-site Scripting (XSS)? Upgrade |
[,1.21.0)
|