CVE-2025-53538

{"id": "CVE-2025-53538", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "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}]}, "published": "2025-07-22T22:15:37.620", "references": [{"url": "https://github.com/OISF/suricata/commit/1d6d331752e933c46aca0ae7a9679b27462246e3", "source": "security-advisories@github.com"}, {"url": "https://github.com/OISF/suricata/commit/7fa88ea9e7d05e07a7864050cfd836b576669720", "source": "security-advisories@github.com"}, {"url": "https://github.com/OISF/suricata/security/advisories/GHSA-qrr7-crgj-cmh3", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-400"}, {"lang": "en", "value": "CWE-770"}]}], "descriptions": [{"lang": "en", "value": "Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions 7.0.10 and below and 8.0.0-beta1 through 8.0.0-rc1, mishandling of data on HTTP2 stream 0 can lead to uncontrolled memory usage, leading to loss of visibility. Workarounds include disabling the HTTP/2 parser, and using a signature like drop http2 any any -> any any (frame:http2.hdr; byte_test:1,=,0,3; byte_test:4,=,0,5; sid: 1;) where the first byte test tests the HTTP2 frame type DATA and the second tests the stream id 0. This is fixed in versions 7.0.11 and 8.0.0."}, {"lang": "es", "value": "Suricata es un motor de red IDS, IPS y NSM desarrollado por la OISF (Open Information Security Foundation) y la comunidad Suricata. En las versiones 7.0.10 y anteriores, y de la 8.0.0-beta1 a la 8.0.0-rc1, la gesti\u00f3n incorrecta de datos en el flujo HTTP2 0 puede provocar un uso incontrolado de memoria, lo que conlleva p\u00e9rdida de visibilidad. Las soluciones alternativas incluyen deshabilitar el analizador HTTP/2 y usar una firma como `drop http2 any any -> any any (frame:http2.hdr; byte_test:1,=,0,3; byte_test:4,=,0,5; sid: 1;''), donde la primera prueba de bytes verifica el tipo de trama HTTP2 `DATA'' y la segunda el ID de flujo 0. Esto se ha corregido en las versiones 7.0.11 y 8.0.0."}], "lastModified": "2025-07-25T15:29:44.523", "sourceIdentifier": "security-advisories@github.com"}