dbcve.org
Matrix Media RepoApplication · T2bot

CVE-2024-52602

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-16
Fix available
A fix is available. Upgrade to 1.3.8 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 Media Repo (MMR) is a highly configurable multi-homeserver media repository for Matrix. Matrix Media Repo (MMR) is vulnerable to server-side request forgery, serving content from a private network it can access, under certain conditions. This is fixed in MMR v1.3.8. Users are advised to upgrade. Restricting which hosts MMR is allowed to contact via (local) firewall rules or a transparent proxy and may provide a workaround for users unable to upgrade.

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 · moderate confidence

Matrix Media Repo (MMR) contains a server-side request forgery (SSRF) vulnerability that allows the application to be coerced into fetching and serving content from private/internal network resources that the MMR server can access. An attacker with the ability to control media requests could potentially reach internal services, metadata, or infrastructure endpoints not intended for external access.

MitigationUpgrade to MMR v1.3.8 or later to obtain the vendor patch. If immediate upgrading is not feasible, implement network-level controls via firewall rules or a transparent proxy to restrict outbound connections from the MMR host to only permitted external destinations.

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
Low
Integrity
None
Availability
None

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

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 if Matrix Media Repo is installed
    Check for the MMR binary or service: look for 'matrix-media-repo' process running, or check system packages/repository for installed MMR. On Linux, commands like 'ps aux | grep -i matrix' or 'dpkg -l | grep -i matrix' may reveal it.
    Affected if Matrix Media Repo is present on the system
  2. Determine the installed MMR version
    Run the MMR binary with version flag: 'matrix-media-repo --version' or check the package version via system package manager (e.g., 'apt list --installed | grep matrix', 'rpm -qa | grep matrix'). Compare against the affected range.
    Affected if Version is less than 1.3.8
  3. Verify the MMR service is network-accessible
    Check the MMR configuration file for bind addresses and ports (commonly in config.yaml or similar). Examine network listeners via 'netstat -tlnp | grep -E "(8000|8008|8448)"' or similar common MMR ports, or review firewall rules to see if the service is exposed to untrusted networks.
    Affected if MMR is listening on a publicly accessible IP or is reachable from untrusted networks
  4. Confirm remote media fetching is enabled
    Review MMR configuration for settings that enable remote media proxying or URL fetching capabilities. Check if the 'url_preview' or similar features that fetch external content are enabled in the config file.
    Affected if Remote media fetching or URL preview features are enabled in the configuration

You are affected if you are running any version of Matrix Media Repo below 1.3.8 that is network-accessible to attackers and has remote media fetching capabilities enabled.

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 to obtain the vendor patch. If immediate upgrading is not feasible, implement network-level controls via firewall rules or a transparent proxy to restrict outbound connections from the MMR host to only permitted external destinations.

Recommended fix High confidence

v1.3.8

  1. Upgrade Matrix Media Repo to version 1.3.8 or later
  2. Verify the upgrade by checking the installed version matches or exceeds v1.3.8
  3. As an alternative for users unable to upgrade, implement network-level restrictions using firewall rules or a transparent proxy to limit MMR's outbound connections to trusted hosts only

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

Fix this in Matrix Media Repo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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