Skip to content

matrix-media-repo (MMR) allows a denial of service through memory exhaustion

Moderate severity GitHub Reviewed Published Jan 16, 2025 in t2bot/matrix-media-repo • Updated Jan 17, 2025

Package

gomod github.com/t2bot/matrix-media-repo (Go)

Affected versions

<= 1.3.7

Patched versions

1.3.8

Description

Impact

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.

Patches

This is fixed in MMR v1.3.8.

Workarounds

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.

References

@turt2live turt2live published to t2bot/matrix-media-repo Jan 16, 2025
Published to the GitHub Advisory Database Jan 16, 2025
Reviewed Jan 16, 2025
Published by the National Vulnerability Database Jan 16, 2025
Last updated Jan 17, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS score

0.043%
(11th percentile)

Weaknesses

CVE ID

CVE-2024-52791

GHSA ID

GHSA-gp86-q8hg-fpxj

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.