Quick answers
- Is CVE-2022-36060 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-36060 being exploited in the wild.
- How severe is CVE-2022-36060?
- Low severity, with a CVSS score of 3.1, published 28 March 2023.
- Which products and versions are affected?
- matrix-react-sdk (npm) SEMVER:introduced=0,fixed=3.53.0.
- Is there a fix for CVE-2022-36060?
- Yes. matrix-react-sdk (npm): upgrade to 3.53.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-36060 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2022-36060?
- Check whether you run matrix-react-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-react-sdk (npm): upgrade to 3.53.0 or later
npm install matrix-react-sdk@3.53.0
Technical details
A prototype pollution vulnerability (CWE-1321) exists in matrix-react-sdk prior to version 3.53.0. The vulnerability is triggered when the SDK processes incoming Matrix events containing specially crafted strings in specific key fields. An unauthenticated remote attacker can exploit this by sending malicious events to a room, leading to 'soft crashes' where specific room views or event tiles fail to render. This is caused by improper control of modifications to object prototype attributes during event processing. The issue is resolved in version 3.53.0.
Affected products
- Matrix.org matrix-react-sdk < 3.53.0
Identifiers
- CVE-2022-36060
- GHSA-2x9c-qwgf-94xr
Timeline
- 2022-08-31: patched: Fixed in version 3.53.0
- 2023-03-28: disclosed: Public advisory published