CVE-2024-52791
T2Bot Matrix-Media-Repo ≤ 1.3.8
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2024-52791 is a medium-severity Memory Allocation with Excessive Size Value (CWE-789) vulnerability in T2Bot Matrix-Media-Repo. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SC-6 (Resource Availability) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-52791 is a memory exhaustion vulnerability (CWE-789) in Matrix Media Repo (MMR), a highly configurable multi-homeserver media repository for the Matrix protocol. During normal operation, MMR fetches resources from other servers, which can respond with excessively large JSON payloads. Parsing these payloads causes MMR to consume significant amounts of memory, potentially leading to exhaustion of available resources. The vulnerability is rated with a CVSS v3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).
Any attacker controlling a server that MMR requests resources from can exploit this issue remotely without authentication or user interaction. By serving oversized JSON responses, the attacker triggers high memory usage in MMR during parsing, resulting in denial-of-service through resource exhaustion and potential service crashes.
The vulnerability is fixed in MMR version 1.3.8, and users are advised to upgrade immediately. For those unable to upgrade, mitigations include configuring forward proxies to block requests to unsafe hosts, setting memory limits on MMR processes with auto-restart capabilities, or running multiple MMR processes concurrently to minimize downtime during restarts. Details are available in the GitHub security advisory (GHSA-gp86-q8hg-fpxj) and release notes for v1.3.8.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-0098
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly rejects or bounds untrusted size values before any allocation occurs.
Resource quotas and priority allocation limit the system-wide impact of an oversized request.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent coding flaws that trust unvalidated size values for allocations.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect and block excessive allocation flaws before deployment.
Secure development lifecycle includes input validation and size checks that prevent unbounded allocations.
Application security requirements mandate bounds checking on size parameters to avoid excessive memory allocation.
Secure architecture principles require resource-limit enforcement that mitigates uncontrolled memory requests.
Secure coding standards directly prohibit allocating memory from untrusted size values without validation.
Capacity management monitors overall resource use but does not prevent individual allocation bugs.