CVE-2024-36403

{"id": "CVE-2024-36403", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "published": "2025-01-16T20:15:32.197", "references": [{"url": "https://en.wikipedia.org/wiki/Leaky_bucket#As_a_meter", "tags": ["Technical Description"], "source": "security-advisories@github.com"}, {"url": "https://github.com/t2bot/matrix-media-repo/security/advisories/GHSA-vc2m-hw89-qjxf", "tags": ["Vendor Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-770"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Matrix Media Repo (MMR) es un repositorio multimedia para m\u00faltiples servidores dom\u00e9sticos altamente configurable para Matrix. MMR anterior a la versi\u00f3n 1.3.5 es vulnerable al consumo ilimitado de disco, donde un adversario no autenticado puede inducirlo a descargar y almacenar en cach\u00e9 grandes cantidades de archivos multimedia remotos. El entorno operativo t\u00edpico de MMR utiliza un almacenamiento similar a S3 como backend, con un almacenamiento respaldado por archivos como una opci\u00f3n alternativa. Las instancias que utilizan un almacenamiento respaldado por archivos o aquellas que alojan por s\u00ed mismas un sistema de almacenamiento S3 son, por lo tanto, vulnerables a un ataque de llenado de disco. Una vez que el disco est\u00e1 lleno, los usuarios autenticados no podr\u00e1n cargar nuevos medios, lo que resultar\u00e1 en una denegaci\u00f3n de servicio. Para las instancias configuradas para utilizar una opci\u00f3n de almacenamiento S3 basada en la nube, esto podr\u00eda resultar en altas tarifas de servicio en lugar de una denegaci\u00f3n de servicio. MMR 1.3.5 introduce un nuevo l\u00edmite de tasa de \"dep\u00f3sito con fugas\" predeterminado para reducir la cantidad de datos que un usuario puede solicitar a la vez. Esto no resuelve el problema por completo, pero limita la capacidad de un usuario no autenticado de solicitar grandes cantidades de datos. Los operadores deben tener en cuenta que la implementaci\u00f3n del contenedor con fugas introducida en MMR 1.3.5 requiere que se reenv\u00ede la direcci\u00f3n IP asociada con la solicitud, para evitar aplicar por error el l\u00edmite de velocidad al proxy inverso. Para evitar este problema, el proxy inverso debe completar el encabezado X-Forwarded-For al enviar la solicitud a MMR. Los operadores que no pueden actualizar pueden desear reducir el tama\u00f1o m\u00e1ximo de archivo que permiten e implementar l\u00edmites de velocidad estrictos, aunque esto puede dar lugar a que se descargue una gran cantidad de datos."}], "lastModified": "2025-08-20T15:19:29.360", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:t2bot:matrix-media-repo:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "0B2BD7DE-DC40-4CC9-89A7-40F3AEDBE012", "versionEndExcluding": "1.3.5"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}