{"uuid": "acbcdcf4-c6b1-4f9e-a2b8-7053fda7238d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "name": "OpenSSL Security Advisory [30th September 2025]", "description": "OpenSSL Security Advisory [30th September 2025]\n===============================================\n\nOut-of-bounds read & write in RFC 3211 KEK Unwrap (CVE-2025-9230)\n=================================================================\n\nSeverity: Moderate\n\nIssue summary: An application trying to decrypt CMS messages encrypted using\npassword based encryption can trigger an out-of-bounds read and write.\n\nImpact summary: This out-of-bounds read may trigger a crash which leads to\nDenial of Service for an application. The out-of-bounds write can cause\na memory corruption which can have various consequences including\na Denial of Service or Execution of attacker-supplied code.\n\nAlthough the consequences of a successful exploit of this vulnerability\ncould be severe, the probability that the attacker would be able to\nperform it is low. Besides, password based (PWRI) encryption support in CMS\nmessages is very rarely used. For that reason the issue was assessed as\nModerate severity according to our Security Policy.\n\nThe FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this\nissue, as the CMS implementation is outside the OpenSSL FIPS module\nboundary.\n\nOpenSSL 3.5, 3.4, 3.3, 3.2, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\n\nOpenSSL 3.5 users should upgrade to OpenSSL 3.5.4.\n\nOpenSSL 3.4 users should upgrade to OpenSSL 3.4.3.\n\nOpenSSL 3.3 users should upgrade to OpenSSL 3.3.5.\n\nOpenSSL 3.2 users should upgrade to OpenSSL 3.2.6.\n\nOpenSSL 3.0 users should upgrade to OpenSSL 3.0.18.\n\nOpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zd.\n(premium support customers only)\n\nOpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zm.\n(premium support customers only)\n\nThis issue was reported on 9th August 2025 by Stanislav Fort (Aisle Research).\nThe fix was developed by Stanislav Fort (Aisle Research) and Viktor Dukhovni.\n\n\nTiming side-channel in SM2 algorithm on 64 bit ARM (CVE-2025-9231) \n=================================================================\n\nSeverity: Moderate\n\nIssue summary: A timing side-channel which could potentially allow remote\nrecovery of the private key exists in the SM2 algorithm implementation on 64 bit\nARM platforms.\n\nImpact summary: A timing side-channel in SM2 signature computations on 64 bit\nARM platforms could allow recovering the private key by an attacker. \n\nWhile remote key recovery over a network was not attempted by the reporter,\ntiming measurements revealed a timing signal which may allow such an attack.\n\nOpenSSL does not directly support certificates with SM2 keys in TLS, and so\nthis CVE is not relevant in most TLS contexts.  However, given that it is\npossible to add support for such certificates via a custom provider, coupled\nwith the fact that in such a custom provider context the private key may be\nrecoverable via remote timing measurements, we consider this to be a Moderate\nseverity issue.\n\nThe FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this\nissue, as SM2 is not an approved algorithm.\n\nOpenSSL 3.1, 3.0, 1.1.1 and 1.0.2 are not vulnerable to this issue.\n\nOpenSSL 3.5, 3.4, 3.3, and 3.2 are vulnerable to this issue.\n\nOpenSSL 3.5 users should upgrade to OpenSSL 3.5.4.\n\nOpenSSL 3.4 users should upgrade to OpenSSL 3.4.3.\n\nOpenSSL 3.3 users should upgrade to OpenSSL 3.3.5.\n\nOpenSSL 3.2 users should upgrade to OpenSSL 3.2.6.\n\nThis issue was reported on 18th August 2025 by Stanislav Fort (Aisle Research)\nThe fix was developed by Stanislav Fort.\n\nOut-of-bounds read in HTTP client no_proxy handling (CVE-2025-9232)\n===================================================================\n\nSeverity: Low\n\nIssue summary: An application using the OpenSSL HTTP client API functions may\ntrigger an out-of-bounds read if the \"no_proxy\" environment variable is set and\nthe host portion of the authority component of the HTTP URL is an IPv6 address.\n\nImpact summary: An out-of-bounds read can trigger a crash which leads to\nDenial of Service for an application.\n\nThe OpenSSL HTTP client API functions can be used directly by applications\nbut they are also used by the OCSP client functions and CMP (Certificate\nManagement Protocol) client implementation in OpenSSL. However the URLs used\nby these implementations are unlikely to be controlled by an attacker.\n\nIn this vulnerable code the out of bounds read can only trigger a crash.\nFurthermore the vulnerability requires an attacker-controlled URL to be\npassed from an application to the OpenSSL function and the user has to have\na \"no_proxy\" environment variable set. For the aforementioned reasons the\nissue was assessed as Low severity.\n\nThe vulnerable code was introduced in the following patch releases:\n3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0.\n\nThe FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this\nissue, as the HTTP client implementation is outside the OpenSSL FIPS module\nboundary.\n\nOpenSSL 3.5, 3.4, 3.3, 3.2 and 3.0 are vulnerable to this issue.\n\nOpenSSL 1.1.1 and 1.0.2 are not affected by this issue.\n\nOpenSSL 3.5 users should upgrade to OpenSSL 3.5.4.\n\nOpenSSL 3.4 users should upgrade to OpenSSL 3.4.3.\n\nOpenSSL 3.3 users should upgrade to OpenSSL 3.3.5.\n\nOpenSSL 3.2 users should upgrade to OpenSSL 3.2.6.\n\nOpenSSL 3.0 users should upgrade to OpenSSL 3.0.18.\n\nThis issue was reported on 16th August 2025 by Stanislav Fort (Aisle Research).\nThe fix was developed by Stanislav Fort (Aisle Research).\n\nGeneral Advisory Notes\n======================\n\nURL for this Security Advisory:\nhttps://openssl-library.org/news/secadv/20250930.txt\n\nNote: the online version of the advisory may be updated with additional details\nover time.\n\nFor details of OpenSSL severity classifications please see:\nhttps://openssl-library.org/policies/general/security-policy/", "creation_timestamp": "2025-10-03T20:56:07.268024+00:00", "timestamp": "2025-10-03T20:56:07.268024+00:00", "related_vulnerabilities": ["CVE-2025-9231", "CVE-2025-9232", "CVE-2025-9230"], "author": {"login": "adulau", "name": "Alexandre Dulaunoy", "uuid": "c933734a-9be8-4142-889e-26e95c752803"}}