Skip to content

matrix-appservice-irc events can be crafted to leak parts of targeted messages from other bridged rooms

Low severity GitHub Reviewed Published Aug 4, 2023 in matrix-org/matrix-appservice-irc • Updated Nov 12, 2023

Package

npm matrix-appservice-irc (npm)

Affected versions

<= 1.0.0

Patched versions

1.0.1

Description

Impact

It was possible to craft an event such that it would leak part of a targeted message event from another bridged room. This required knowing an event ID to target.

Patches

Please upgrade to 1.0.1.

Workarounds

You can set the matrixHandler.eventCacheSize config value to 0 to workaround this bug. However, this may impact performance.

Credits

Discovered and reported by Val Lorentz.

For more information

If you have any questions or comments about this advisory email us at [email protected].

References

@Half-Shot Half-Shot published to matrix-org/matrix-appservice-irc Aug 4, 2023
Published to the GitHub Advisory Database Aug 4, 2023
Reviewed Aug 4, 2023
Published by the National Vulnerability Database Aug 4, 2023
Last updated Nov 12, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N

EPSS score

0.079%
(36th percentile)

Weaknesses

CVE ID

CVE-2023-38700

GHSA ID

GHSA-c7hh-3v6c-fj4q

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.