dbcve.org
Matrix Media RepoApplication · T2bot

CVE-2024-52791

HIGH · 7.5 CVSS v3.1 Published 2025-01-16
Fix available
A fix is available. Upgrade to 1.3.8 or later.
See remediation →
84/100
Remediation priority · High
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 Media Repo (MMR) is a highly configurable multi-homeserver media repository for Matrix. MMR makes requests to other servers as part of normal operation, and these resource owners can return large amounts of JSON back to MMR for parsing. In parsing, MMR can consume large amounts of memory and exhaust available memory. This is fixed in MMR v1.3.8. Users are advised to upgrade. For users unable to upgrade; forward proxies can be configured to block requests to unsafe hosts. Alternatively, MMR processes can be configured with memory limits and auto-restart. Running multiple MMR processes concurrently can help ensure a restart does not overly impact users.

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 Media Repo (MMR) has a memory exhaustion vulnerability where parsing JSON responses from remote Matrix servers can consume excessive memory, leading to denial of service. A malicious or compromised remote server can return extremely large JSON payloads that cause MMR to allocate all available memory.

MitigationUpgrade to MMR v1.3.8 or later. If immediate upgrading is not feasible, configure forward proxies to block requests to untrusted hosts, implement process memory limits with auto-restart, or run multiple MMR processes to ensure availability during incidents.

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
Matrix Media RepoApplication
Affected:< 1.3.8

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
High

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

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 installed MMR version
    Run the version check command for Matrix Media Repo (commonly 'mmr --version', 'm --version', or check via package manager)
    Affected if The installed version is below 1.3.8
  2. Confirm MMR is processing remote Matrix server responses
    Review MMR configuration for upstream Matrix server connections or federation settings that allow fetching content from remote servers
    Affected if MMR is configured to fetch or parse JSON responses from remote Matrix servers
  3. Assess network exposure
    Check if MMR is exposed to untrusted or external Matrix servers (examine bind addresses, firewall rules, or federation ACLs)
    Affected if MMR can receive JSON responses from untrusted or compromised remote Matrix servers

You are affected if the installed Matrix Media Repo version is below 1.3.8 and the service processes JSON responses from remote Matrix servers, which is the default operational mode.

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 1.3.8 or later
Fixed in 1.3.8
Interim mitigation

Upgrade to MMR v1.3.8 or later. If immediate upgrading is not feasible, configure forward proxies to block requests to untrusted hosts, implement process memory limits with auto-restart, or run multiple MMR processes to ensure availability during incidents.

Recommended fix High confidence

Matrix Media Repo v1.3.8

  1. Backup your current Matrix Media Repo installation and configuration files
  2. Download Matrix Media Repo v1.3.8 from the official GitHub repository
  3. Replace the existing MMR binary with the new v1.3.8 binary
  4. Restart the MMR service to apply the update
  5. Monitor the service to ensure it runs correctly without memory issues

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

Fix this in Matrix Media Repo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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