Skip to content

Parsing issue in matrix-org/node-irc leading to room takeovers

High severity GitHub Reviewed Published Sep 13, 2022 in matrix-org/matrix-appservice-irc • Updated Jan 29, 2023

Package

npm matrix-appservice-irc (npm)

Affected versions

< 0.35.0

Patched versions

0.35.0

Description

Impact

Attackers can specify a specific string of characters, which would confuse the bridge into combining an attacker-owned channel and an existing channel, allowing them to grant themselves permissions in the channel.

Patched

The vulnerability has been patched in matrix-appservice-irc 0.35.0.

Workarounds

Disable dynamic channel joining via dynamicChannels.enabled to prevent users from joining new channels, which prevents any new channels being bridged outside of what is already bridged, and what is specified in the config.

References

Credits

Discovered and reported by Val Lorentz.

For more information

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

References

@dkasak dkasak published to matrix-org/matrix-appservice-irc Sep 13, 2022
Published by the National Vulnerability Database Sep 13, 2022
Published to the GitHub Advisory Database Sep 15, 2022
Reviewed Sep 15, 2022
Last updated Jan 29, 2023

Severity

High

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
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.104%
(44th percentile)

Weaknesses

CVE ID

CVE-2022-39203

GHSA ID

GHSA-xvqg-mv25-rwvw

Source code

Credits

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