Advisories ยป MGASA-2015-0111

Updated openssl packages fix security vulnerabilities

Publication date: 19 Mar 2015
Type: security
Affected Mageia releases : 4
CVE: CVE-2015-0286 , CVE-2015-0287 , CVE-2015-0289 , CVE-2015-0293 , CVE-2015-0209 , CVE-2015-0288

Description

Updated openssl packages fix security vulnerabilities:

The function ASN1_TYPE_cmp will crash with an invalid read if an attempt is
made to compare ASN.1 boolean types. Since ASN1_TYPE_cmp is used to check
certificate signature algorithm consistency this can be used to crash any
certificate verification operation and exploited in a DoS attack. Any
application which performs certificate verification is vulnerable including
OpenSSL clients and servers which enable client authentication
(CVE-2015-0286).

Reusing a structure in ASN.1 parsing may allow an attacker to cause
memory corruption via an invalid write. Such reuse is and has been
strongly discouraged and is believed to be rare. Certificate parsing,
OpenSSL clients, and OpenSSL servers are not affected (CVE-2015-0287).

The PKCS#7 parsing code does not handle missing outer ContentInfo correctly.
An attacker can craft malformed ASN.1-encoded PKCS#7 blobs with
missing content and trigger a NULL pointer dereference on parsing.
OpenSSL clients and servers are not affected (CVE-2015-0289).

A malicious client can trigger an OPENSSL_assert (i.e., an abort) in
servers that both support SSLv2 and enable export cipher suites by sending
a specially crafted SSLv2 CLIENT-MASTER-KEY message (CVE-2015-0293).

A malformed EC private key file consumed via the d2i_ECPrivateKey function
could cause a use after free condition. This, in turn, could cause a double
free in several private key parsing functions (such as d2i_PrivateKey
or EVP_PKCS82PKEY) and could lead to a DoS attack or memory corruption
for applications that receive EC private keys from untrusted
sources. This scenario is considered rare (CVE-2015-0209).

The function X509_to_X509_REQ will crash with a NULL pointer dereference if
the certificate key is invalid. This function is rarely used in practice
(CVE-2015-0288).
                

References

SRPMS

4/core