[Pkg-openssl-devel] Bug#918717: Bug#918717: Bug#918717: openssl: wrong signature type on a specific website with openssl.cnf shipped in debian

[Kurt Roeckx]

On Tue, Jan 08, 2019 at 07:30:01PM +0100, Sebastian Andrzej Siewior wrote:
> On 2019-01-08 17:40:04 [+0100], Jérémy Lal wrote:
> > Package: openssl
> > Version: 1.1.1a-1
> > Severity: normal
> > 
> > Hi,
> > 
> > curl https://portal.gexpertise.fr/GexPortal
> > returns an error,
> > 
> > however (you need nodejs 10.15~dfsg-8 for this file to be available - the file in itself
> > is there to be able to run upstream tests suites)
> > OPENSSL_CONF=/usr/include/nodejs/openssl.cnf curl https://portal.gexpertise.fr/GexPortal
> > does work
> 
> The server is vurnable to OpenSSL Padding Oracle vulnerability
> (CVE-2016-2107) [0].
> 
> The problem is that the remote server is signing the certificate wit
> SHA1 instead something stronger:
> |No client certificate CA names sent
> |Peer signing digest: SHA1
> |Peer signature type: RSA
> |Server Temp Key: ECDH, P-256, 256 bits
> 
> Kurt did we want to enable SHA1 for DEFAULT at SECLEVEL=2?

No, we do not want to enable it at level 2.

The server in question should support SHA256, but because of a bug
always uses SHA1. The commit that fixed it in the 1.0.1 branch,
which I think is what they are running, is
4e05aedbcab7f7f83a887e952ebdcc5d4f2291e4, which is a commit from
2014.


Kurt