Bug 14987 - openssl new security issues fixed upstream in 1.0.1k
Summary: openssl new security issues fixed upstream in 1.0.1k
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact: Sec team
URL: http://lwn.net/Vulnerabilities/629235/
Whiteboard: has_procedure MGA4-32-OK mga4-64-ok a...
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2015-01-08 18:48 CET by David Walser
Modified: 2015-01-12 19:16 CET (History)
2 users (show)

See Also:
Source RPM: openssl-1.0.1e-8.8.mga4.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2015-01-08 18:48:05 CET
Upstream has issued an advisory today (January 8):
https://www.openssl.org/news/secadv_20150108.txt

Freeze push requested for Cauldron.

We'll need patches for Mageia 4.

Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2015-01-09 18:12:08 CET
Mandriva has issued an advisory for this today (January 9):
http://www.mandriva.com/en/support/security/advisories/mbs1/MDVSA-2015%3A019/

Oden has also uploaded an updated package for Mageia 4.

Advisory:
========================

Updated openssl packages fix security vulnerabilities:

A carefully crafted DTLS message can cause a segmentation fault in
OpenSSL due to a NULL pointer dereference. This could lead to a Denial
Of Service attack (CVE-2014-3571).

A memory leak can occur in the dtls1_buffer_record function under
certain conditions. In particular this could occur if an attacker
sent repeated DTLS records with the same sequence number but for the
next epoch. The memory leak could be exploited by an attacker in a
Denial of Service attack through memory exhaustion (CVE-2015-0206).

When openssl is built with the no-ssl3 option and a SSL v3 ClientHello
is received the ssl method would be set to NULL which could later
result in a NULL pointer dereference (CVE-2014-3569).

An OpenSSL client will accept a handshake using an ephemeral ECDH
ciphersuite using an ECDSA certificate if the server key exchange
message is omitted. This effectively removes forward secrecy from
the ciphersuite (CVE-2014-3572).

An OpenSSL client will accept the use of an RSA temporary key in
a non-export RSA key exchange ciphersuite. A server could present
a weak temporary key and downgrade the security of the session
(CVE-2015-0204).

An OpenSSL server will accept a DH certificate for client
authentication without the certificate verify message. This effectively
allows a client to authenticate without the use of a private key. This
only affects servers which trust a client certificate authority which
issues certificates containing DH keys: these are extremely rare and
hardly ever encountered (CVE-2015-0205).

OpenSSL accepts several non-DER-variations of certificate signature
algorithm and signature encodings. OpenSSL also does not enforce a
match between the signature algorithm between the signed and unsigned
portions of the certificate. By modifying the contents of the signature
algorithm or the encoding of the signature, it is possible to change
the certificate's fingerprint. This does not allow an attacker to
forge certificates, and does not affect certificate verification or
OpenSSL servers/clients in any other way. It also does not affect
common revocation mechanisms. Only custom applications that rely
on the uniqueness of the fingerprint (e.g. certificate blacklists)
may be affected (CVE-2014-8275).

Bignum squaring (BN_sqr) may produce incorrect results on some
platforms, including x86_64. This bug occurs at random with a very
low probability, and is not known to be exploitable in any way,
though its exact impact is difficult to determine (CVE-2014-3570).

The updated packages have been upgraded to the 1.0.1k version where
these security flaws have been fixed.

References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3569
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3570
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3571
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3572
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8275
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0204
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0205
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0206
https://www.openssl.org/news/secadv_20150108.txt
http://www.mandriva.com/en/support/security/advisories/mbs1/MDVSA-2015%3A019/
========================

Updated packages in core/updates_testing:
========================
openssl-1.0.1k-1.mga4
libopenssl-engines1.0.0-1.0.1k-1.mga4
libopenssl1.0.0-1.0.1k-1.mga4
libopenssl-devel-1.0.1k-1.mga4
libopenssl-static-devel-1.0.1k-1.mga4

from openssl-1.0.1k-1.mga4.src.rpm

Assignee: bugsquad => qa-bugs

Comment 2 David Walser 2015-01-09 18:21:22 CET
Testing procedure:
https://wiki.mageia.org/en/QA_procedure:Openssl

Whiteboard: (none) => has_procedure

Comment 3 William Kenney 2015-01-10 20:00:18 CET
In VirtualBox, M4, KDE, 32-bit

Package(s) under test:
openssl

default install of openssl

[root@localhost wilcal]# urpmi openssl
Package openssl-1.0.1e-8.8.mga4.i586 is already installed

Server under test is at 192.168.1.88:443

[wilcal@localhost ~]$ openssl version
OpenSSL 1.0.1e 11 Feb 2013
[wilcal@localhost ~]$ openssl speed
Doing mdc2 for 3s on 16 size blocks: 2419640 mdc2's in 3.00s
[wilcal@localhost ~]$ openssl speed rsa
Doing 512 bit private rsa's for 10s: 81417 512 bit private RSA's in 9.99s
[wilcal@localhost ~]$ openssl s_client -connect localhost:443
CONNECTED(00000003)
depth=0 CN = localhost, OU = default httpd cert for localhost, emailAddress = root@localhost
verify error:num=18:self signed certificate
verify return:1
From M4 system at 192.168.1.2:
[wilcal@shermanm4 ~]$ openssl s_client -connect 192.168.1.88:443
CONNECTED(00000003)
depth=0 CN = localhost, OU = default httpd cert for localhost, emailAddress = root@localhost
verify error:num=18:self signed certificate
verify return:1
openssl s_client -connect localhost:443

install openssl from updates_testing

[root@localhost wilcal]# urpmi openssl
Package openssl-1.0.1k-1.mga4.i586 is already installed

[wilcal@localhost ~]$ openssl version
OpenSSL 1.0.1k 8 Jan 2015
[wilcal@localhost ~]$ openssl speed
Doing mdc2 for 3s on 16 size blocks: 2420180 mdc2's in 3.00s
[wilcal@localhost ~]$ openssl speed rsa
Doing 512 bit private rsa's for 10s: 80138 512 bit private RSA's in 9.99s
[wilcal@localhost ~]$ openssl s_client -connect localhost:443
CONNECTED(00000003)
depth=0 CN = localhost, OU = default httpd cert for localhost, emailAddress = root@localhost
verify error:num=18:self signed certificate
verify return:1
From M4 system at 192.168.1.2:
[wilcal@shermanm4 ~]$ openssl s_client -connect 192.168.1.88:443
CONNECTED(00000003)
depth=0 CN = localhost, OU = default httpd cert for localhost, emailAddress = root@localhost
verify error:num=18:self signed certificate
verify return:1

Test platform:
Intel Core i7-2600K Sandy Bridge 3.4GHz
GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo
GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB
RTL8111/8168B PCI Express 1Gbit Ethernet
DRAM 16GB (4 x 4GB)
Mageia 4 64-bit, Nvidia driver
virtualbox-4.3.10-1.1.mga4.x86_64
virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64

CC: (none) => wilcal.int
Whiteboard: has_procedure => has_procedure MGA4-32-OK

Comment 4 claire robinson 2015-01-11 16:24:28 CET
Testing complete mga4 64

Validating. I'll upload the advisory later.

Keywords: (none) => validated_update
Whiteboard: has_procedure MGA4-32-OK => has_procedure MGA4-32-OK mga4-64-ok
CC: (none) => sysadmin-bugs

Comment 5 Rémi Verschelde 2015-01-11 18:38:27 CET
Advisory uploaded.

Whiteboard: has_procedure MGA4-32-OK mga4-64-ok => has_procedure MGA4-32-OK mga4-64-ok advisory

Comment 6 Mageia Robot 2015-01-11 20:54:55 CET
An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGASA-2015-0022.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED

David Walser 2015-01-12 19:16:56 CET

URL: (none) => http://lwn.net/Vulnerabilities/629235/


Note You need to log in before you can comment on or make changes to this bug.