Skip to content

Matrix Media Repo (MMR) allows Server-Side Request Forgery (SSRF) on redirects and federation

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

Matrix Media Repo (MMR) is vulnerable to server-side request forgery, serving content from a private network it can access, under certain conditions.

Patches

This is fixed in MMR v1.3.8.

Workarounds

Restricting which hosts MMR is allowed to contact via (local) firewall rules or a transparent proxy.

References

https://owasp.org/www-community/attacks/Server_Side_Request_Forgery
https://learn.snyk.io/lesson/ssrf-server-side-request-forgery/
https://www.agwa.name/blog/post/preventing_server_side_request_forgery_in_golang

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

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:L/UI:N/S:C/C:L/I:N/A:N

EPSS score

0.062%
(29th percentile)

Weaknesses

CVE ID

CVE-2024-52602

GHSA ID

GHSA-r6jg-jfv6-2fjv

Source code

Credits

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