CVE-2024-36403 Denial of service/high operating costs through unauthenticated downloads in Matrix Media Repo
Unauthenticated attackers can exhaust disk space or incur high cloud costs by triggering unbounded media downloads in Matrix Media Repo.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-36403?
CVE-2024-36403 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 before version 1.3.5 is vulnerable to unbounded disk consumption, where an unauthenticated adversary can induce it to download and cache large amounts of remote media files. MMR's typical operating environment uses S3-like storage as a backend, with file-backed store as an alternative option. Instances using a file-backed store or those which self-host an S3 storage system are therefore vulnerable to a disk fill attack. Once the disk is full, authenticated users will be unable to upload new media, resulting in denial of service. For instances configured to use a cloud-based S3 storage option, this could result in high service fees instead of a denial of service. MMR 1.3.5 introduces a new default-on "leaky bucket" rate limit to reduce the amount of data a user can request at a time. This does not fully address the issue, but does limit an unauthenticated user's ability to request large amounts of data. Operators should note that the leaky bucket implementation introduced in MMR 1.3.5 requires the IP address associated with the request to be forwarded, to avoid mistakenly applying the rate limit to the reverse proxy instead. To avoid this issue, the reverse proxy should populate the X-Forwarded-For header when sending the request to MMR. Operators who cannot update may wish to lower the maximum file size they allow and implement harsh rate limits, though this can still lead to a large amount of data to be downloaded.
Weakness: CWE-770
Which versions are affected by CVE-2024-36403?
3 open source packages ship an affected version, including github.com/t2bot/matrix-media-repo. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/t2bot/matrix-media-repo Go | All versions | 1.3.5 |
github.com/t2bot/matrix-media-repo Go | All versions | 1.3.5 |
github.com/t2bot/matrix-media-repo Go | All versions | 1.3.5 |
Products include T2bot Matrix-Media-Repo.
How do I fix CVE-2024-36403?
Upgrade github.com/t2bot/matrix-media-repo to 1.3.5 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2024-36403 being exploited?
There is no known exploitation of CVE-2024-36403 in the wild and no public exploit code.
Other vulnerabilities in t2bot matrix-media-repo
- CVE-2024-56515 Untrusted file formats can be thumbnailed, invoking potentially further untrusted decoders in Matrix Media Repo
- CVE-2024-36402 Unauthenticated writes to the media repository allow planting of problematic content in Matrix Media Repo
- CVE-2024-52791 Denial of service through memory exhaustion in Matrix Media Repo
- CVE-2024-52602 Server-Side Request Forgery (SSRF) on redirects and federation in Matrix Media Repo
Sources
Also known as GHSA-vc2m-hw89-qjxf, GO-2025-3401.