# CVE-2024-52791: Denial of service through memory exhaustion in Matrix Media Repo

> Attackers can cause denial of service in Matrix Media Repo by sending large JSON responses that exhaust server memory during parsing.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-gp86-q8hg-fpxj, GO-2025-3398

## What is CVE-2024-52791?

CVE-2024-52791 is a medium-severity denial of service vulnerability in t2bot matrix-media-repo, published on 16 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

## Which versions are affected by CVE-2024-52791?

3 open source packages ship an affected version, including github.com/t2bot/matrix-media-repo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/t2bot/matrix-media-repo` | Go | All versions | 1.3.8 |
| `github.com/t2bot/matrix-media-repo` | Go | All versions | 1.3.8 |
| `github.com/t2bot/matrix-media-repo` | Go | All versions | 1.3.8 |

Products: T2bot Matrix-Media-Repo.

## How do I fix CVE-2024-52791?

Upgrade github.com/t2bot/matrix-media-repo to 1.3.8 or later.

## Is CVE-2024-52791 being exploited?

There is no known exploitation of CVE-2024-52791 in the wild and no public exploit code.

## Other vulnerabilities in t2bot matrix-media-repo

- [CVE-2024-56515](https://insights.sbomify.com/CVE-2024-56515/): Untrusted file formats can be thumbnailed, invoking potentially further untrusted decoders in Matrix Media Repo (medium 6.8)
- [CVE-2024-36402](https://insights.sbomify.com/CVE-2024-36402/): Unauthenticated writes to the media repository allow planting of problematic content in Matrix Media Repo (medium 5.3)
- [CVE-2024-36403](https://insights.sbomify.com/CVE-2024-36403/): Denial of service/high operating costs through unauthenticated downloads in Matrix Media Repo (medium 5.3)
- [CVE-2024-52602](https://insights.sbomify.com/CVE-2024-52602/): Server-Side Request Forgery (SSRF) on redirects and federation in Matrix Media Repo (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52791 and fix it if it is affected.

What it is: CVE-2024-52791 is a medium-severity denial of service vulnerability in t2bot matrix-media-repo, published on 16 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-52791 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/t2bot/matrix-media-repo (Go): affected all versions; fixed in 1.3.8
- github.com/t2bot/matrix-media-repo (Go): affected all versions; fixed in 1.3.8
- github.com/t2bot/matrix-media-repo (Go): affected all versions; fixed in 1.3.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-52791/ (Markdown: https://insights.sbomify.com/CVE-2024-52791/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-52791
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-52791
- OSV: https://osv.dev/vulnerability/CVE-2024-52791

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-52791/
Summaries are generated and may contain mistakes; the official description above is the record.