Quick answers
- Is CVE-2022-39236 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-39236 being exploited in the wild.
- How severe is CVE-2022-39236?
- Low severity, with a CVSS score of 3.1, published 29 September 2022.
- Which products and versions are affected?
- matrix-js-sdk (npm) SEMVER:introduced=17.1.0-rc.1,fixed=19.7.0.
- Is there a fix for CVE-2022-39236?
- Yes. matrix-js-sdk (npm): upgrade to 19.7.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-39236 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2022-39236?
- Check whether you run matrix-js-sdk (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- matrix-js-sdk (npm): upgrade to 19.7.0 or later
npm install matrix-js-sdk@19.7.0
Technical details
This vulnerability is a logic error in how matrix-js-sdk processes beacon events defined in Matrix Spec Proposal 3488. Improperly formed beacon events can trigger improper data handling in the SDK, disrupting normal operation and potentially causing data loss or corruption. The attack vector is network-based and requires low privileges (an authenticated user or external attacker sending malformed events). The SDK may continue to appear functional while excluding or corrupting runtime data. The vulnerability affects versions 17.1.0-rc.1 through 19.6.x and is patched in v19.7.0. Workarounds include redacting malicious events, clearing storage, or restarting the client.
Affected products
- matrix-org matrix-js-sdk 17.1.0-rc.1 through 19.6.x
Identifiers
- CVE-2022-39236
- GHSA-hvv8-5v86-r45x
Timeline
- 2022-09-28: disclosed: Publicly disclosed on GitHub and NVD
- 2022-09-28: patched: Fixed in matrix-js-sdk v19.7.0
- 2022-09-29: other: OSV entry published