Matrix Javascript Sdk 17.1.0 Release Candidate 1 for Node.js
Approved changes feed: RSS · Atom
cpe:2.3:a:matrix:javascript_sdk:17.1.0:rc1:*:*:*:node.js:*:*
part: a version: 17.1.0 update: rc1
| Vendor | Matrix (eeffbdfc-c7a5-5b43-a123-a772af0b6d34) |
|---|---|
| Product | Javascript Sdk (7a25111b-e34f-50c0-99ed-23de32687860) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/matrix-org/matrix-js-sdk |
purl2cpe | 2026-06-01 10:13:24.341393 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-39236 |
vulnerable | 2026-06-08 05:47:18.403630 |
Matrix Javascript SDK improper beacon events can cause availability issues
MEDIUM (4.3)
Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Starting with version 17.1.0-rc.1, improperly formed beacon events 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. This is patched in matrix-js-sdk v19.7.0. Redacting applicable events, waiting for the sync processor to store data, and restarting the client are possible workarounds. 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.
Published: 2022-09-28T00:00:00.000Z
Updated: 2025-04-23T16:55:17.226Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.