dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-50336

MEDIUM · 5.3 CVSS v4.0 Published 2024-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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-js-sdk is a Matrix messaging protocol Client-Server SDK for JavaScript. matrix-js-sdk before 34.11.0 is vulnerable to client-side path traversal via crafted MXC URIs. A malicious room member can trigger clients based on the matrix-js-sdk to issue arbitrary authenticated GET requests to the client's homeserver. Fixed in matrix-js-sdk 34.11.1.

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-js-sdk before version 34.11.0 contains a client-side path traversal vulnerability via crafted MXC (Matrix Content) URIs. A malicious room member can exploit this to trick clients into issuing arbitrary authenticated GET requests to the homeserver, potentially exfiltrating sensitive data or accessing unauthorized resources.

MitigationUpgrade matrix-js-sdk to version 34.11.1 or later to patch the path traversal vulnerability in MXC URI handling. Organizations using this SDK in their Matrix client applications should prioritize this update.

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

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify matrix-js-sdk version
    Inspect the package.json file in your project or run 'npm list matrix-js-sdk' or 'yarn list matrix-js-sdk' to retrieve the installed version
    Affected if The installed version is before 34.11.0 (e.g., 34.10.0, 34.9.0, etc.)
  2. Locate the SDK installation
    Check node_modules/matrix-js-sdk/package.json for the version field, or look for the SDK in your dependency lock file (package-lock.json or yarn.lock)
    Affected if The version resolved from dependencies is below 34.11.0
  3. Confirm MXC URI processing is in use
    Search your codebase for usage of Matrix content URIs (mxc://) or SDK methods that handle media/content URLs such as getUrl or content repository methods
    Affected if Your application processes MXC URIs and the SDK version is below 34.11.0
  4. Verify authenticated requests are possible
    Confirm the client application uses authentication (access tokens) when making requests to the homeserver, as the attack leverages authenticated GET requests
    Affected if The application makes authenticated requests to the homeserver and uses a vulnerable SDK version

You are affected if your matrix-js-sdk installation is version 34.10.0 or any earlier version, AND your application processes Matrix content URIs (mxc://) from room members.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade matrix-js-sdk to version 34.11.1 or later to patch the path traversal vulnerability in MXC URI handling. Organizations using this SDK in their Matrix client applications should prioritize this update.

Recommended fix High confidence

34.11.1

  1. Check the current version of matrix-js-sdk in use by examining package.json or running npm list matrix-js-sdk
  2. Upgrade matrix-js-sdk to version 34.11.1 or later using: npm install matrix-js-sdk@^34.11.1 or yarn upgrade matrix-js-sdk@^34.11.1
  3. Verify the upgrade was successful by checking the installed version matches 34.11.1 or later
  4. Test that the Matrix client functionality works correctly after the upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50336 — 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-2024-50336 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