[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipfire-scm
Subject:    [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 9a11c96b8a90e6eeb676226553b76307
From:       Michael Tremer <git () ipfire ! org>
Date:       2021-03-25 14:38:00
Message-ID: 4F5nlD460dz2xdm () people01 ! haj ! ipfire ! org
[Download RAW message or body]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  9a11c96b8a90e6eeb676226553b76307b9abdb47 (commit)
      from  1ac60db42ef50d5a0b8f2a435432c68759d1d36b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 9a11c96b8a90e6eeb676226553b76307b9abdb47
Author: Michael Tremer <michael.tremer@ipfire.org>
Date:   Thu Mar 25 14:36:34 2021 +0000

    openssl: Update to 1.1.1k
    
    From https://www.openssl.org/news/secadv/20210325.txt:
    
    OpenSSL Security Advisory [25 March 2021]
    =========================================
    
    CA certificate check bypass with X509_V_FLAG_X509_STRICT (CVE-2021-3450)
    ========================================================================
    
    Severity: High
    
    The X509_V_FLAG_X509_STRICT flag enables additional security checks of the
    certificates present in a certificate chain. It is not set by default.
    
    Starting from OpenSSL version 1.1.1h a check to disallow certificates in
    the chain that have explicitly encoded elliptic curve parameters was added
    as an additional strict check.
    
    An error in the implementation of this check meant that the result of a
    previous check to confirm that certificates in the chain are valid CA
    certificates was overwritten. This effectively bypasses the check
    that non-CA certificates must not be able to issue other certificates.
    
    If a "purpose" has been configured then there is a subsequent opportunity
    for checks that the certificate is a valid CA.  All of the named "purpose"
    values implemented in libcrypto perform this check.  Therefore, where
    a purpose is set the certificate chain will still be rejected even when the
    strict flag has been used. A purpose is set by default in libssl client and
    server certificate verification routines, but it can be overridden or
    removed by an application.
    
    In order to be affected, an application must explicitly set the
    X509_V_FLAG_X509_STRICT verification flag and either not set a purpose
    for the certificate verification or, in the case of TLS client or server
    applications, override the default purpose.
    
    OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these
    versions should upgrade to OpenSSL 1.1.1k.
    
    OpenSSL 1.0.2 is not impacted by this issue.
    
    This issue was reported to OpenSSL on 18th March 2021 by Benjamin Kaduk
    from Akamai and was discovered by Xiang Ding and others at Akamai. The fix was
    developed by Tomáš Mráz.
    
    NULL pointer deref in signature_algorithms processing (CVE-2021-3449)
    =====================================================================
    
    Severity: High
    
    An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation
    ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits
    the signature_algorithms extension (where it was present in the initial
    ClientHello), but includes a signature_algorithms_cert extension then a NULL
    pointer dereference will result, leading to a crash and a denial of service
    attack.
    
    A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which
    is the default configuration). OpenSSL TLS clients are not impacted by this
    issue.
    
    All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions
    should upgrade to OpenSSL 1.1.1k.
    
    OpenSSL 1.0.2 is not impacted by this issue.
    
    This issue was reported to OpenSSL on 17th March 2021 by Nokia. The fix was
    developed by Peter Kästle and Samuel Sapalski from Nokia.
    
    Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/{oldcore/100 => core/156}/filelists/openssl | 0
 lfs/openssl                                                  | 4 ++--
 2 files changed, 2 insertions(+), 2 deletions(-)
 copy config/rootfiles/{oldcore/100 => core/156}/filelists/openssl (100%)

Difference in files:
diff --git a/config/rootfiles/core/156/filelists/openssl b/config/rootfiles/core/156/filelists/openssl
new file mode 120000
index 000000000..e011a9266
--- /dev/null
+++ b/config/rootfiles/core/156/filelists/openssl
@@ -0,0 +1 @@
+../../../common/openssl
\ No newline at end of file
diff --git a/lfs/openssl b/lfs/openssl
index a50d686f0..c56c24af0 100644
--- a/lfs/openssl
+++ b/lfs/openssl
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 1.1.1j
+VER        = 1.1.1k
 
 THISAPP    = openssl-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -78,7 +78,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = cccaa064ed860a2b4d1303811bf5c682
+$(DL_FILE)_MD5 = c4e7d95f782b08116afa27b30393dd27
 
 install : $(TARGET)
 


hooks/post-receive
--
IPFire 2.x development tree


_______________________________________________
IPFire-SCM mailing list
IPFire-SCM@lists.ipfire.org
https://lists.ipfire.org/mailman/listinfo/ipfire-scm


[prev in list] [next in list] [prev in thread] [next in thread]