CVE-2024-36402

matrix-media-repo (MMR) allows unauthenticated writes to the media repository, which may allow planting of problematic content

Workarounds

Though extremely limited, server operators can use more strict rate limits based on IP address.

References

https://github.com/matrix-org/matrix-spec-proposals/pull/3916

MMR before version 1.3.5 allows, by design, unauthenticated remote participants to trigger a download and caching of remote media from a remote homeserver to the local media repository. Such content then also becomes available for download from the local homeserver in an unauthenticated way. The implication is that unauthenticated remote adversaries can use this functionality to plant problematic content into the media repository.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2024-36402 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.3.5); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

MMR 1.3.5 introduces a partial mitigation in the form of new endpoints which require authentication for media downloads. The unauthenticated endpoints will be frozen in a future release, closing the attack vector.

1. What is CVE-2024-36402? CVE-2024-36402 is a medium-severity improper authentication vulnerability in github.com/t2bot/matrix-media-repo (go), affecting versions < 1.3.5. It is fixed in 1.3.5. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2024-36402? CVE-2024-36402 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/t2bot/matrix-media-repo are affected by CVE-2024-36402? github.com/t2bot/matrix-media-repo (go) versions < 1.3.5 is affected.
4. Is there a fix for CVE-2024-36402? Yes. CVE-2024-36402 is fixed in 1.3.5. Upgrade to this version or later.
5. Is CVE-2024-36402 exploitable, and should I be worried? Whether CVE-2024-36402 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-36402 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-36402? Upgrade github.com/t2bot/matrix-media-repo to 1.3.5 or later.

Other vulnerabilities in github.com/t2bot/matrix-media-repo