OpenSSL CVEs (20250930): CVE-2025-9230, CVE-2025-9231, CVE-2025-9232

[tianon]

Filing this as a place to write down my thoughts (more accurately, copy the thoughts from upstream that I think are the most relevant):

https://openssl-library.org/news/secadv/20250930.txt

https://lists.debian.org/debian-security-announce/2025/msg00181.html

Out-of-bounds read & write in RFC 3211 KEK Unwrap (CVE-2025-9230)

Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used.

Timing side-channel in SM2 algorithm on 64 bit ARM (CVE-2025-9231)

OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts.

Out-of-bounds read in HTTP client no_proxy handling (CVE-2025-9232)

However the URLs used by these implementations are unlikely to be controlled by an attacker.

In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a "no_proxy" environment variable set.

So the short version of my thoughts is that while these are important and we will update the image to include them, I don't think we need to rush it (especially given we just did a rebuild and none of these are actually critical or even likely to be exploited in a meaningful way).

Users who disagree with that assessment (more accurately, those who have a stricter threat model than average or who are doing something unusual enough to be within the attack vectors) can and should update the affected packages (https://packages.debian.org/source/trixie/openssl) in their own dependent images (RUN apt-get install --update -y libssl3t64, for example).