All :
Just a heads up. I hope this lands in ports *really* fast.
--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
PS: no FreeBSD on Raspberry Pi5 yet. Too many ugly blobs still.
-------- Forwarded Message --------
Subject: OpenSSL Security Advisory
Date: Tue, 11 Feb 2025 16:54:29 +0100
From: Tomas Mraz <to...@openssl.org>
To: openssl-project <openssl-proj...@openssl.org>, openssl-users
<openssl-us...@openssl.org>
OpenSSL Security Advisory [11th February 2025]
==============================================
RFC7250 handshakes with unauthenticated servers don't abort as expected
(CVE-2024-12797)
========================================================================================
Severity: High
Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to
authenticate a
server may fail to notice that the server was not authenticated, because
handshakes don't abort as expected when the SSL_VERIFY_PEER verification
mode
is set.
Impact summary: TLS and DTLS connections using raw public keys may be
vulnerable to man-in-middle attacks when server authentication failure
is not
detected by clients.
RPKs are disabled by default in both TLS clients and TLS servers.
The issue only arises when TLS clients explicitly enable RPK use
by the server, and the server, likewise, enables sending of an RPK
instead of an X.509 certificate chain. The affected clients are
those that then rely on the handshake to fail when the server's RPK
fails to match one of the expected public keys, by setting the
verification mode to SSL_VERIFY_PEER.
Clients that enable server-side raw public keys can still find out that
raw public key verification failed by calling SSL_get_verify_result(),
and those that do, and take appropriate action, are not affected. This
issue was introduced in the initial implementation of RPK support in
OpenSSL 3.2.
The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by
this issue.
OpenSSL 3.1, 3.0, 1.1.1 and 1.0.2 are also not affected by this issue.
OpenSSL 3.4, 3.3 and 3.2 are vulnerable to this issue.
OpenSSL 3.4 users should upgrade to OpenSSL 3.4.1.
OpenSSL 3.3 users should upgrade to OpenSSL 3.3.2.
OpenSSL 3.2 users should upgrade to OpenSSL 3.2.4.
This issue was reported on 18th December 2024 by Apple Inc.
The fix was developed by Viktor Dukhovni.
General Advisory Notes
======================
URL for this Security Advisory:
https://openssl-library.org/news/secadv/20250211.txt
Note: the online version of the advisory may be updated with additional
details over time.
For details of OpenSSL severity classifications please see:
https://openssl-library.org/policies/general/security-policy/
