CVE-2024-52791

{
  "id": "CVE-2024-52791",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2024-52791",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2025-01-16T19:58:44.951492Z"
        }
      }
    ],
    "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:N/I:N/A:H",
          "integrityImpact": "NONE",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "NONE"
        },
        "impactScore": 3.6,
        "exploitabilityScore": 3.9
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "t2bot",
          "product": "matrix-media-repo",
          "versions": [
            {
              "status": "affected",
              "version": "< 1.3.8"
            }
          ]
        }
      ]
    }
  ],
  "published": "2025-01-16T20:15:32.667",
  "references": [
    {
      "url": "https://github.com/t2bot/matrix-media-repo/releases/tag/v1.3.8",
      "tags": [
        "Release Notes"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/t2bot/matrix-media-repo/security/advisories/GHSA-gp86-q8hg-fpxj",
      "tags": [
        "Vendor Advisory"
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-789"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "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 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."
    },
    {
      "lang": "es",
      "value": "Matrix Media Repo (MMR) es un repositorio multimedia de múltiples servidores domésticos altamente configurable para Matrix. MMR realiza solicitudes a otros servidores como parte de la operación normal, y estos propietarios de recursos pueden devolver grandes cantidades de JSON a MMR para su análisis. Durante el análisis, MMR puede consumir grandes cantidades de memoria y agotar la memoria disponible. Esto se solucionó en MMR v1.3.8. Se recomienda a los usuarios que actualicen. Para los usuarios que no puedan actualizar, se pueden configurar servidores proxy de reenvío para bloquear solicitudes a hosts no seguros. Alternativamente, los procesos MMR se pueden configurar con límites de memoria y reinicio automático. Ejecutar varios procesos MMR simultáneamente puede ayudar a garantizar que un reinicio no afecte demasiado a los usuarios."
    }
  ],
  "lastModified": "2026-06-17T08:07:38.180",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:t2bot:matrix-media-repo:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "9B68F8B2-5C9C-425E-8B26-582B49848883",
              "versionEndExcluding": "1.3.8"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "security-advisories@github.com"
}