CVE-2022-39250: Matrix js sdk Matrix-js-sdk Subject To User Impersonation Vulnerability

HIGH
Advisory Identifier: GHSA-5w8r-8pgj-5jmf
CVSS 8.6
CWE-322 CWE-287
Published
Advisory Summary

CVE-2022-39250 is a HIGH (CVSS 8.6) matrix-js-sdk subject to user impersonation vulnerability (CWE-322: Key Exchange without Entity Authentication) affecting Matrix js sdk libraries in the npm ecosystem. The issue involves matrix-js-sdk subject to user impersonation due to key/device identifier confusion in sas verification. Remediation is available by upgrading affected packages to version 19.7.0.

CVE-2022-39250 at a Glance

CVE Identifier CVE-2022-39250
GHSA Identifier GHSA-5w8r-8pgj-5jmf
Severity HIGH
CVSS v3.1 Base Score 8.6
CWE Classification CWE-322: Key Exchange without Entity Authentication
Affected Product Matrix js sdk
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2022-39250

To remediate this vulnerability, upgrade all affected Matrix js sdk dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

matrix-js-sdk fixed: 19.7.0
npm install matrix-js-sdk@19.7.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls matrix-js-sdk

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2022-39250, inspect your project dependencies using npm:

npm ls matrix-js-sdk

Analyze the terminal output to locate any version of Matrix js sdk in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 19.7.0), your application is affected.

Note: The npm ls matrix-js-sdk command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-322: Key Exchange without Entity Authentication, where the product performs a key exchange with an actor without verifying the identity of that actor. In Matrix js sdk, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impact An attacker cooperating with a malicious homeserver could interfere with the verification flow between two users, injecting its own cross-signing user identity in place of one of the users’ identities, leading to the other device trusting/verifying the user identity under the control of the homeserver instead of the intended one. The vulnerability is a bug in the matrix-js-sdk, caused by checking and signing user identities and devices in two separate steps, and inadequately fixing the keys to be signed between those steps. Even though the attack is partly made possible due to the design decision of treating cross-signing user identities as Matrix devices on the server side (with their device ID set to the public part of the user identity key), no other examined implementations were vulnerable. ## Patches The matrix-js-sdk has been modified to double check that the key signed is the one that was verified instead of just referencing the key by ID. An additional check has been made to report an error when one of the device ID matches a cross-signing key. ## Workarounds As this attack requires coordination between a malicious homeserver and an attacker -- if you trust your homeserver no particular workaround is needed. As a potential way of detecting compromise, it’s possible to review your device list or the device list of other users for devices with IDs in the form of a base64 cross-signing key (`5XaczGNlfz0bl8R1IX5qn+tBoue2tWJqLMh+SDUuvCk`) instead of classical device ID (`SEHACYDHMG`). ## References Blog post: https://matrix.org/blog/2022/09/28/upgrade-now-to-address-encryption-vulns-in-matrix-sdks-and-clients ## For more information If you have any questions or comments about this advisory, e-mail us at security@matrix.org

CVE-2022-39250 Affected Matrix js sdk Versions

1 component(s)
Fixed Versions:
19.7.0
Product / Package Ecosystem Affected Versions Fixed Version
matrix-js-sdk
npm
< 19.7.0
19.7.0

References

Frequently Asked Questions

What is CVE-2022-39250?
CVE-2022-39250 is a security vulnerability in Matrix js sdk involving matrix-js-sdk subject to user impersonation due to key/device identifier confusion in SAS verification under CWE-322: Key Exchange without Entity Authentication.
Which Matrix js sdk versions are affected?
Affected versions include releases prior to 19.7.0 across affected packages: matrix-js-sdk.
What version fixes CVE-2022-39250?
Upgrading to 19.7.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is matrix-js-sdk affected?
Yes, matrix-js-sdk is affected in releases prior to 19.7.0. Upgrade your dependency to 19.7.0 or later.
What is the CVSS score of CVE-2022-39250?
CVE-2022-39250 has a CVSS v3.1 base score of 8.6 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N.
What CWE is associated with CVE-2022-39250?
CVE-2022-39250 is classified under CWE-322: Key Exchange without Entity Authentication (The product performs a key exchange with an actor without verifying the identity of that actor.).
How can I check npm dependencies for CVE-2022-39250?
Run the dependency tree command: 'npm ls matrix-js-sdk'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5w8r-8pgj-5jmf",
  "modified" : "2022-11-01T13:24:57Z",
  "published" : "2022-09-30T22:46:50Z",
  "aliases" : [ "CVE-2022-39250" ],
  "summary" : "matrix-js-sdk subject to user impersonation due to key/device identifier confusion in SAS verification",
  "details" : "## Impact\n\nAn attacker cooperating with a malicious homeserver could interfere with the verification flow between two users, injecting its own cross-signing user identity in place of one of the users’ identities, leading to the other device trusting/verifying the user identity under the control of the homeserver instead of the intended one.\n\nThe vulnerability is a bug in the matrix-js-sdk, caused by checking and signing user identities and devices in two separate steps, and inadequately fixing the keys to be signed between those steps.\n\nEven though the attack is partly made possible due to the design decision of treating cross-signing user identities as Matrix devices on the server side (with their device ID set to the public part of the user identity key), no other examined implementations were vulnerable.\n\n## Patches\n\nThe matrix-js-sdk has been modified to double check that the key signed is the one that was verified instead of just referencing the key by ID. An additional check has been made to report an error when one of the device ID matches a cross-signing key.\n\n## Workarounds\n\nAs this attack requires coordination between a malicious homeserver and an attacker -- if you trust your homeserver no particular workaround is needed. \n\nAs a potential way of detecting compromise, it’s possible to review your device list or the device list of other users for devices with IDs in the form of a base64 cross-signing key (`5XaczGNlfz0bl8R1IX5qn+tBoue2tWJqLMh+SDUuvCk`) instead of classical device ID (`SEHACYDHMG`).\n\n## References\nBlog post: https://matrix.org/blog/2022/09/28/upgrade-now-to-address-encryption-vulns-in-matrix-sdks-and-clients\n\n## For more information\nIf you have any questions or comments about this advisory, e-mail us at security@matrix.org\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "matrix-js-sdk"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "19.7.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-5w8r-8pgj-5jmf"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-39250"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/matrix-org/matrix-js-sdk/commit/a587d7c36026fe1fcf93dfff63588abee359be76"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/matrix-org/matrix-js-sdk"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/matrix-org/matrix-js-sdk/releases/tag/v19.7.0"
  }, {
    "type" : "WEB",
    "url" : "https://matrix.org/blog/2022/09/28/upgrade-now-to-address-encryption-vulns-in-matrix-sdks-and-clients"
  }, {
    "type" : "WEB",
    "url" : "https://security.gentoo.org/glsa/202210-35"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287", "CWE-322" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-09-30T22:46:50Z",
    "nvd_published_at" : "2022-09-29T13:15:00Z"
  }
}