CVE-2022-24666

{"id": "CVE-2022-24666", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 5.0, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:N/C:N/I:N/A:P", "authentication": "NONE", "integrityImpact": "NONE", "accessComplexity": "LOW", "availabilityImpact": "PARTIAL", "confidentialityImpact": "NONE"}, "acInsufInfo": false, "impactScore": 2.9, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 10.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"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}]}, "published": "2022-02-09T23:15:20.233", "references": [{"url": "https://github.com/apple/swift-nio-http2/security/advisories/GHSA-ccw9-q5h2-8c2w", "tags": ["Third Party Advisory"], "source": "cve@forums.swift.org"}, {"url": "https://github.com/apple/swift-nio-http2/security/advisories/GHSA-ccw9-q5h2-8c2w", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "cve@forums.swift.org", "description": [{"lang": "en", "value": "CWE-130"}]}, {"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "NVD-CWE-Other"}]}], "descriptions": [{"lang": "en", "value": "A program using swift-nio-http2 is vulnerable to a denial of service attack, caused by a network peer sending a specially crafted HTTP/2 frame. This attack affects all swift-nio-http2 versions from 1.0.0 to 1.19.1. This vulnerability is caused by a logical error when parsing a HTTP/2 HEADERS frame where the frame contains priority information without any other data. This logical error caused confusion about the size of the frame, leading to a parsing error. This parsing error immediately crashes the entire process. Sending a HEADERS frame with HTTP/2 priority information does not require any special permission, so any HTTP/2 connection peer may send such a frame. For clients, this means any server to which they connect may launch this attack. For servers, anyone they allow to connect to them may launch such an attack. The attack is low-effort: it takes very little resources to send an appropriately crafted frame. The impact on availability is high: receiving the frame immediately crashes the server, dropping all in-flight connections and causing the service to need to restart. It is straightforward for an attacker to repeatedly send appropriately crafted frames, so attackers require very few resources to achieve a substantial denial of service. The attack does not have any confidentiality or integrity risks in and of itself: swift-nio-http2 is parsing the frame in memory-safe code, so the crash is safe. However, sudden process crashes can lead to violations of invariants in services, so it is possible that this attack can be used to trigger an error condition that has confidentiality or integrity risks. The risk can be mitigated if untrusted peers can be prevented from communicating with the service. This mitigation is not available to many services. The issue is fixed by rewriting the parsing code to correctly handle the condition. The issue was found by automated fuzzing by oss-fuzz."}, {"lang": "es", "value": "Un programa usando swift-nio-http2 es vulnerable a un ataque de denegaci\u00f3n de servicio, causado por un compa\u00f1ero de red que env\u00eda una trama HTTP/2 especialmente dise\u00f1ada. Este ataque afecta a todas las versiones de swift-nio-http2 desde 1.0.0 hasta 1.19.1. Esta vulnerabilidad est\u00e1 causada por un error l\u00f3gico cuando es analizada una trama HTTP/2 HEADERS en la que la trama contiene informaci\u00f3n de prioridad sin ning\u00fan otro dato. Este error l\u00f3gico causaba una confusi\u00f3n sobre el tama\u00f1o de la trama, conllevando a un error de an\u00e1lisis. Este error de an\u00e1lisis bloquea inmediatamente todo el proceso. El env\u00edo de una trama HEADERS con informaci\u00f3n de prioridad HTTP/2 no requiere ning\u00fan permiso especial, por lo que cualquier par de conexi\u00f3n HTTP/2 puede enviar una trama de este tipo. Para los clientes, esto significa que cualquier servidor al que son conectados puede lanzar este ataque. Para los servidores, cualquier persona a la que permitan conectarse puede lanzar este ataque. El ataque es de bajo esfuerzo: son necesarios muy pocos recursos para enviar una trama apropiadamente dise\u00f1ada. El impacto en la disponibilidad es alto: la recepci\u00f3n de la trama bloquea inmediatamente el servidor, cayendo todas las conexiones en curso y causando la necesidad de reiniciar el servicio. Es sencillo para un atacante enviar repetidamente tramas apropiadamente dise\u00f1adas, por lo que atacantes necesitan muy pocos recursos para lograr una denegaci\u00f3n de servicio sustancial. El ataque no presenta ning\u00fan riesgo de confidencialidad o integridad en s\u00ed mismo: swift-nio-http2 est\u00e1 analizando la trama en c\u00f3digo seguro para la memoria, por lo que el bloqueo es seguro. Sin embargo, los bloqueos repentinos de procesos pueden conllevar a violaciones de invariantes en los servicios, por lo que es posible que este ataque pueda ser usado para desencadenar una condici\u00f3n de error que tenga riesgos de confidencialidad o integridad. El riesgo puede mitigarse si puede evitarse que los compa\u00f1eros que no son confiables puedan comunicarse con el servicio. Esta mitigaci\u00f3n no est\u00e1 disponible para muchos servicios. El problema es corregido al reescribir el c\u00f3digo de an\u00e1lisis para manejar correctamente la condici\u00f3n. El problema ha sido detectado mediante un fuzzing automatizado con oss-fuzz"}], "lastModified": "2024-11-21T06:50:49.417", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:apple:swiftnio_http\\/2:*:*:*:*:*:swift:*:*", "vulnerable": true, "matchCriteriaId": "DAF5D763-09A3-4427-82F7-EF049316E6E8", "versionEndExcluding": "1.19.2", "versionStartIncluding": "1.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "cve@forums.swift.org"}