CWE
20
Advisory Published
CVE Published
Updated

CVE-2023-32323: Input Validation

First published: Wed May 24 2023(Updated: )

### Impact A malicious user on a Synapse homeserver X with permission to create certain state events can disable outbound federation from X to an arbitrary homeserver Y. Synapse instances with federation disabled are not affected. #### Details The Matrix protocol allows homeservers to provide an `invite_room_state` field on a [room invite](https://spec.matrix.org/v1.5/client-server-api/#mroommember) containing a [summary of room state](https://spec.matrix.org/v1.5/client-server-api/#stripped-state). In versions of Synapse up to and including v1.73.0, Synapse did not limit the size of `invite_room_state`, meaning that it was possible to create an arbitrarily large invite event. An attacker with an account on a vulnerable Synapse homeserver X could exploit this by having X create an over-sized invite event in a room with a user from another homeserver Y. Once acknowledged by the invitee's homeserver, the invite event would be sent in a batch of events to Y. If the malicious invite is so large that the entire batch is rejected as too large, X's outgoing traffic to Y would become "stuck", meaning that messages and state events created by X would remain unseen by Y. ### Patches Synapse 1.74 refuses to create oversized `invite_room_state` fields. Server operators should upgrade to Synapse 1.74 or newer urgently. ### Workarounds There are no robust workarounds. This attack needs an account on Synapse homeserver X to deny federation from X to another homeserver Y. As a partial mitigation, Synapse operators can disable open registration to limit the ability of attackers to create new accounts on homeserver X. If homeserver X has been attacked in this way, restarting it will resume outgoing federation by entering "catchup mode". For catchup mode to ignore the oversized invites, every attacked room must have a correctly-sized event sent by X which is newer than any oversized invite. This is difficult to arrange, and does not prevent the attacker from repeating their attack. ### References - https://github.com/matrix-org/synapse/issues/14492 was caused by this issue. - https://github.com/matrix-org/synapse/issues/14642 includes the patch described above. ### For more information If you have any questions or comments about this advisory, e-mail us at [security@matrix.org](mailto:security@matrix.org).

Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
Matrix Synapse<1.74.0
pip/matrix-synapse<1.74.0
1.74.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is CVE-2023-32323?

    CVE-2023-32323 is a vulnerability in Synapse, an open-source Matrix homeserver, that allows a malicious user to disable outbound federation from one homeserver to another.

  • How does CVE-2023-32323 affect Synapse instances?

    Synapse instances with federation disabled are not affected by CVE-2023-32323.

  • What is the impact of CVE-2023-32323?

    The impact of CVE-2023-32323 is that it can disable outbound federation from one Synapse homeserver to another.

  • How can I fix CVE-2023-32323?

    To fix CVE-2023-32323, upgrade Synapse to version 1.74.0 or higher.

  • Are there any references or resources related to CVE-2023-32323?

    Yes, you can find more information about CVE-2023-32323 in the following links: [GitHub Advisory](https://github.com/matrix-org/synapse/security/advisories/GHSA-f3wc-3vxv-xmvr), [GitHub Issue](https://github.com/matrix-org/synapse/issues/14492), [GitHub Pull Request](https://github.com/matrix-org/synapse/pull/14642).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203