CVE-2024-2511

{"id": "CVE-2024-2511", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.9, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 2.2}]}, "published": "2024-04-08T14:15:07.660", "references": [{"url": "https://github.com/openssl/openssl/commit/7e4d731b1c07201ad9374c1cd9ac5263bdf35bce", "source": "[email protected]"}, {"url": "https://github.com/openssl/openssl/commit/b52867a9f618bb955bed2a3ce3db4d4f97ed8e5d", "source": "[email protected]"}, {"url": "https://github.com/openssl/openssl/commit/e9d7083e241670332e0443da0f0d4ffb52829f08", "source": "[email protected]"}, {"url": "https://github.openssl.org/openssl/extended-releases/commit/5f8d25770ae6437db119dfc951e207271a326640", "source": "[email protected]"}, {"url": "https://www.openssl.org/news/secadv/20240408.txt", "source": "[email protected]"}, {"url": "http://www.openwall.com/lists/oss-security/2024/04/08/5", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/openssl/openssl/commit/7e4d731b1c07201ad9374c1cd9ac5263bdf35bce", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/openssl/openssl/commit/b52867a9f618bb955bed2a3ce3db4d4f97ed8e5d", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/openssl/openssl/commit/e9d7083e241670332e0443da0f0d4ffb52829f08", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.openssl.org/openssl/extended-releases/commit/5f8d25770ae6437db119dfc951e207271a326640", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://security.netapp.com/advisory/ntap-20240503-0013/", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://www.openssl.org/news/secadv/20240408.txt", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "[email protected]", "description": [{"lang": "en", "value": "CWE-1325"}]}], "descriptions": [{"lang": "en", "value": "Issue summary: Some non-default TLS server configurations can cause unbounded\nmemory growth when processing TLSv1.3 sessions\n\nImpact summary: An attacker may exploit certain server configurations to trigger\nunbounded memory growth that would lead to a Denial of Service\n\nThis problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is\nbeing used (but not if early_data support is also configured and the default\nanti-replay protection is in use). In this case, under certain conditions, the\nsession cache can get into an incorrect state and it will fail to flush properly\nas it fills. The session cache will continue to grow in an unbounded manner. A\nmalicious client could deliberately create the scenario for this failure to\nforce a Denial of Service. It may also happen by accident in normal operation.\n\nThis issue only affects TLS servers supporting TLSv1.3. It does not affect TLS\nclients.\n\nThe FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL\n1.0.2 is also not affected by this issue."}, {"lang": "es", "value": "Resumen del problema: algunas configuraciones de servidor TLS no predeterminadas pueden causar un crecimiento ilimitado de la memoria al procesar sesiones TLSv1.3. Resumen de impacto: un atacante puede explotar ciertas configuraciones del servidor para desencadenar un crecimiento ilimitado de la memoria que conducir\u00eda a una denegaci\u00f3n de servicio. Este problema puede ocurrir en TLSv1.3 si se utiliza la opci\u00f3n SSL_OP_NO_TICKET no predeterminada (pero no si tambi\u00e9n se configura la compatibilidad con early_data y se utiliza la protecci\u00f3n antirrepetici\u00f3n predeterminada). En este caso, bajo ciertas condiciones, el cach\u00e9 de la sesi\u00f3n puede entrar en un estado incorrecto y no se vaciar\u00e1 correctamente a medida que se llena. La cach\u00e9 de la sesi\u00f3n seguir\u00e1 creciendo de forma ilimitada. Un cliente malintencionado podr\u00eda crear deliberadamente el escenario para que este fallo fuerce una denegaci\u00f3n de servicio. Tambi\u00e9n puede ocurrir por accidente durante el funcionamiento normal. Este problema solo afecta a los servidores TLS que admiten TLSv1.3. No afecta a los clientes TLS. Los m\u00f3dulos FIPS en 3.2, 3.1 y 3.0 no se ven afectados por este problema. OpenSSL 1.0.2 tampoco se ve afectado por este problema."}], "lastModified": "2025-11-03T22:16:50.900", "sourceIdentifier": "[email protected]"}