Skip to content

Improper beacon events in matrix-js-sdk can result in availability issues

Moderate severity GitHub Reviewed Published Sep 28, 2022 in matrix-org/matrix-js-sdk • Updated Jan 30, 2023

Package

npm matrix-js-sdk (npm)

Affected versions

>= 17.1.0-rc.1, < 19.7.0

Patched versions

19.7.0

Description

Impact

Improperly formed beacon events (from MSC3488) can disrupt or impede the matrix-js-sdk from functioning properly, potentially impacting the consumer's ability to process data safely. Note that the matrix-js-sdk can appear to be operating normally but be excluding or corrupting runtime data presented to the consumer.

Patches

This is patched in matrix-js-sdk v19.7.0

Workarounds

Redacting applicable events, waiting for the sync processor to store data, and restarting the client can often fix it. Alternatively, redacting the applicable events and clearing all storage will fix the further perceived issues.

Downgrading to an unaffected version, noting that such a version may be subject to other vulnerabilities, will additionally resolve the issue.

References

N/A - This was a logic error in the SDK.

For more information

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

References

@turt2live turt2live published to matrix-org/matrix-js-sdk Sep 28, 2022
Published by the National Vulnerability Database Sep 28, 2022
Published to the GitHub Advisory Database Sep 29, 2022
Reviewed Sep 29, 2022
Last updated Jan 30, 2023

Severity

Moderate

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
None
Integrity
None
Availability
Low

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:N/I:N/A:L

EPSS score

0.142%
(51st percentile)

Weaknesses

CVE ID

CVE-2022-39236

GHSA ID

GHSA-hvv8-5v86-r45x

Source code

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