Impact

The matrix-appservice-irc before version 2.0.0 can be exploited to leak the truncated body of a message if a malicious user sends a Matrix reply to an event ID they don't have access to. As a precondition to the attack, the malicious user needs to know the event ID of the message they want to leak, as well as to be joined to both the Matrix room and the IRC channel it is bridged to.

The message reply containing the leaked message content is visible to IRC channel members when this happens.

Patches

matrix-appservice-irc 2.0.0 checks whether the user has permission to view an event before constructing a reply. Administrators should upgrade to this version.

Workarounds

It's possible to limit the amount of information leaked by setting a reply template that doesn't contain the original message. See these lines in the configuration file.

References

matrix-org/matrix-appservice-irc#1799

For more information

If you have any questions or comments about this advisory, please email us at security at matrix.org.

References

• GHSA-wm4w-7h2q-3pf7
• matrix-org/matrix-appservice-irc#1799
• matrix-org/matrix-appservice-irc@4af7d30
• https://nvd.nist.gov/vuln/detail/CVE-2024-32000
• https://github.com/matrix-org/matrix-appservice-irc/blob/d5d67d1d3ea3f0f6962a0af2cc57b56af3ad2129/config.sample.yaml#L601-L604