dbcve.org
React SdkFramework / library · Matrix

CVE-2022-36060

MEDIUM · 5.3 CVSS v3.1 Published 2023-03-28
Fix available
A fix is available. Upgrade to 3.53.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
matrix-react-sdk is a Matrix chat protocol SDK for React Javascript. Events sent with special strings in key places can temporarily disrupt or impede the matrix-react-sdk from functioning properly, such as by causing room or event tile crashes. The remainder of the application can appear functional, though certain rooms/events will not be rendered. This issue has been fixed in matrix-react-sdk 3.53.0 and users are advised to upgrade. There are no known workarounds for this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

matrix-react-sdk versions before 3.53.0 fail to properly sanitize or handle special string characters in event data, causing room and event tile crashes during rendering. This leads to selective denial of service where certain rooms or events cannot be viewed while the rest of the application remains functional.

MitigationUpgrade matrix-react-sdk to version 3.53.0 or later. No workarounds exist; the fix must be applied at the SDK level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
React SdkFramework / library
Affected:< 3.53.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate matrix-react-sdk package
    Check your project's package.json file or run 'npm list matrix-react-sdk' to see the installed version
    Affected if The version listed is below 3.53.0 or no version is shown (meaning it may be resolving a vulnerable transitive dependency)
  2. Verify the exact version number
    Run 'npm view matrix-react-sdk version' to confirm the latest version, then compare with your installed version from step 1
    Affected if Your installed version is less than 3.53.0 (e.g., 3.52.0, 3.51.0, etc.)
  3. Check for nested or bundled dependencies
    Run 'npm ls matrix-react-sdk' to see if multiple versions exist in your dependency tree
    Affected if A version below 3.53.0 appears anywhere in the dependency tree, even as a transitive dependency
  4. Identify the application context
    Determine if your application uses Element Web, Element iOS, Element Android, or a custom Matrix client built on this SDK
    Affected if Your application is built on matrix-react-sdk and displays room events to users
  5. Review runtime behavior (optional)
    Monitor for JavaScript errors or crashes when rendering rooms with events containing Unicode special characters (emoji, ZWJ sequences, or unusual formatting)
    Affected if Users experience room or event tile crashes and the SDK version is below 3.53.0

You are affected if your installed matrix-react-sdk version is anything less than 3.53.0, regardless of how the application is deployed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.53.0 or later
Fixed in 3.53.0
Interim mitigation

Upgrade matrix-react-sdk to version 3.53.0 or later. No workarounds exist; the fix must be applied at the SDK level.

Recommended fix High confidence

matrix-react-sdk 3.53.0

  1. 1. Identify the current version of matrix-react-sdk in use by checking package.json or package-lock.json
  2. 2. Run npm update matrix-react-sdk or yarn upgrade matrix-react-sdk to update to the latest version
  3. 3. Verify the update was successful by checking the installed version (npm list matrix-react-sdk or yarn list matrix-react-sdk)
  4. 4. Ensure version 3.53.0 or later is installed
  5. 5. Rebuild and redeploy the application to incorporate the updated SDK

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in React Sdk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36060 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data