CVE-2025-5372

{"id": "CVE-2025-5372", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "secalert@redhat.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.0, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "LOW", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 3.4, "exploitabilityScore": 1.6}]}, "published": "2025-07-04T06:15:24.930", "references": [{"url": "https://access.redhat.com/security/cve/CVE-2025-5372", "source": "secalert@redhat.com"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2369388", "source": "secalert@redhat.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "secalert@redhat.com", "description": [{"lang": "en", "value": "CWE-682"}]}], "descriptions": [{"lang": "en", "value": "A flaw was found in libssh versions built with OpenSSL versions older than 3.0, specifically in the ssh_kdf() function responsible for key derivation. Due to inconsistent interpretation of return values where OpenSSL uses 0 to indicate failure and libssh uses 0 for success\u2014the function may mistakenly return a success status even when key derivation fails. This results in uninitialized cryptographic key buffers being used in subsequent communication, potentially compromising SSH sessions' confidentiality, integrity, and availability."}, {"lang": "es", "value": "Se encontr\u00f3 una falla en las versiones de libssh compiladas con versiones de OpenSSL anteriores a la 3.0, espec\u00edficamente en la funci\u00f3n ssh_kdf(), responsable de la derivaci\u00f3n de claves. Debido a la interpretaci\u00f3n inconsistente de los valores de retorno, donde OpenSSL usa 0 para indicar un fallo y libssh usa 0 para \u00e9xito, la funci\u00f3n puede devolver err\u00f3neamente un estado de \u00e9xito incluso cuando la derivaci\u00f3n de claves falla. Esto provoca que se utilicen b\u00faferes de claves criptogr\u00e1ficas sin inicializar en comunicaciones posteriores, lo que podr\u00eda comprometer la confidencialidad, integridad y disponibilidad de las sesiones SSH."}], "lastModified": "2025-07-08T16:18:53.607", "sourceIdentifier": "secalert@redhat.com"}