CVE-2025-8671

{"id": "CVE-2025-8671", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "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-08-13T13:15:34.790", "references": [{"url": "https://galbarnahum.com/made-you-reset", "source": "[email protected]"}, {"url": "https://github.com/h2o/h2o/commit/4729b661e3c6654198d2cc62997e1af58bef4b80", "source": "[email protected]"}, {"url": "https://github.com/h2o/h2o/security/advisories/GHSA-mrjm-qq9m-9mjq", "source": "[email protected]"}, {"url": "https://gitlab.isc.org/isc-projects/bind9/-/issues/5325", "source": "[email protected]"}, {"url": "https://kb.cert.org/vuls/id/767506", "source": "[email protected]"}, {"url": "https://support2.windriver.com/index.php?page=security-notices", "source": "[email protected]"}, {"url": "https://varnish-cache.org/security/VSV00017.html", "source": "[email protected]"}, {"url": "https://www.fastlystatus.com/incident/377810", "source": "[email protected]"}, {"url": "https://www.suse.com/support/kb/doc/?id=000021980", "source": "[email protected]"}, {"url": "http://www.openwall.com/lists/oss-security/2025/08/13/6", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://www.openwall.com/lists/oss-security/2025/09/18/1", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://deepness-lab.org/publications/madeyoureset/", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/Kong/kong/discussions/14731", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/envoyproxy/envoy/issues/40739", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/varnish/hitch/issues/397", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://www.imperva.com/blog/madeyoureset-turning-http-2-server-against-itself/", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://www.kb.cert.org/vuls/id/767506", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://gitlab.isc.org/isc-projects/bind9/-/issues/5325", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-404"}]}], "descriptions": [{"lang": "en", "value": "A mismatch caused by client-triggered server-sent stream resets between HTTP/2 specifications and the internal architectures of some HTTP/2 implementations may result in excessive server resource consumption leading to denial-of-service (DoS). By opening streams and then rapidly triggering the server to reset them\u2014using malformed frames or flow control errors\u2014an attacker can exploit incorrect stream accounting. Streams reset by the server are considered closed at the protocol level, even though backend processing continues. This allows a client to cause the server to handle an unbounded number of concurrent streams on a single connection. This CVE will be updated as affected product details are released."}, {"lang": "es", "value": "Una discrepancia causada por el restablecimiento de flujos enviados por el servidor, activados por el cliente, entre las especificaciones HTTP/2 y las arquitecturas internas de algunas implementaciones de HTTP/2 puede resultar en un consumo excesivo de recursos del servidor, lo que resulta en una denegaci\u00f3n de servicio (DoS). Al abrir flujos y luego activar r\u00e1pidamente el servidor para que los restablezca (mediante tramas malformadas o errores de control de flujo), un atacante puede explotar la contabilidad incorrecta de los flujos. Los flujos restablecidos por el servidor se consideran cerrados a nivel de protocolo, aunque el procesamiento del backend contin\u00fae. Esto permite que un cliente haga que el servidor gestione un n\u00famero ilimitado de flujos simult\u00e1neos en una sola conexi\u00f3n. Esta CVE se actualizar\u00e1 a medida que se publiquen los detalles de los productos afectados."}], "lastModified": "2025-11-04T22:16:44.813", "sourceIdentifier": "[email protected]"}