CVE-2022-38152

{"id": "CVE-2022-38152", "metrics": {"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-08-31T17:15:08.297", "references": [{"url": "http://packetstormsecurity.com/files/170604/wolfSSL-Session-Resumption-Denial-Of-Service.html", "tags": ["Exploit", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "http://seclists.org/fulldisclosure/2023/Jan/7", "tags": ["Exploit", "Mailing List", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://blog.trailofbits.com/2023/01/12/wolfssl-vulnerabilities-tlspuffin-fuzzing-ssh/", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://github.com/tlspuffin/tlspuffin", "tags": ["Not Applicable"], "source": "cve@mitre.org"}, {"url": "https://github.com/wolfSSL/wolfssl/pull/5468", "tags": ["Exploit", "Patch", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://github.com/wolfSSL/wolfssl/releases", "tags": ["Release Notes"], "source": "cve@mitre.org"}, {"url": "https://www.wolfssl.com/docs/security-vulnerabilities/", "tags": ["Vendor Advisory"], "source": "cve@mitre.org"}, {"url": "http://packetstormsecurity.com/files/170604/wolfSSL-Session-Resumption-Denial-Of-Service.html", "tags": ["Exploit", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://seclists.org/fulldisclosure/2023/Jan/7", "tags": ["Exploit", "Mailing List", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://blog.trailofbits.com/2023/01/12/wolfssl-vulnerabilities-tlspuffin-fuzzing-ssh/", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/tlspuffin/tlspuffin", "tags": ["Not Applicable"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/wolfSSL/wolfssl/pull/5468", "tags": ["Exploit", "Patch", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/wolfSSL/wolfssl/releases", "tags": ["Release Notes"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://www.wolfssl.com/docs/security-vulnerabilities/", "tags": ["Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-754"}]}], "descriptions": [{"lang": "en", "value": "An issue was discovered in wolfSSL before 5.5.0. When a TLS 1.3 client connects to a wolfSSL server and SSL_clear is called on its session, the server crashes with a segmentation fault. This occurs in the second session, which is created through TLS session resumption and reuses the initial struct WOLFSSL. If the server reuses the previous session structure (struct WOLFSSL) by calling wolfSSL_clear(WOLFSSL* ssl) on it, the next received Client Hello (that resumes the previous session) crashes the server. Note that this bug is only triggered when resuming sessions using TLS session resumption. Only servers that use wolfSSL_clear instead of the recommended SSL_free; SSL_new sequence are affected. Furthermore, wolfSSL_clear is part of wolfSSL's compatibility layer and is not enabled by default. It is not part of wolfSSL's native API."}, {"lang": "es", "value": "Se ha detectado un problema en wolfSSL versiones anteriores a 5.5.0. Cuando un cliente TLS versi\u00f3n 1.3 es conectado a un servidor wolfSSL y es llamado a SSL_clear en su sesi\u00f3n, el servidor es bloqueado con un fallo de segmentaci\u00f3n. Esto ocurre en la segunda sesi\u00f3n, que es creada mediante la reanudaci\u00f3n de la sesi\u00f3n TLS y re\u00fasa la estructura inicial WOLFSSL. Si el servidor re\u00fasa la estructura de sesi\u00f3n anterior (struct WOLFSSL) llamando a wolfSSL_clear(WOLFSSL* ssl) sobre ella, el siguiente Client Hello recibido (que reanuda la sesi\u00f3n anterior) bloquea el servidor. Tenga en cuenta que este fallo s\u00f3lo es producido cuando son reanudadas las sesiones usando la reanudaci\u00f3n de sesi\u00f3n TLS. S\u00f3lo est\u00e1n afectados los servidores que usan wolfSSL_clear en lugar de la secuencia recomendada SSL_free; SSL_new. Adem\u00e1s, wolfSSL_clear forma parte de la capa de compatibilidad de wolfSSL y no est\u00e1 habilitada por defecto. No forma parte de la API nativa de wolfSSL"}], "lastModified": "2024-11-21T07:15:54.057", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:wolfssl:wolfssl:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "429B1D46-A7C6-4510-89E4-88222C933D0B", "versionEndExcluding": "5.5.0"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}