CVE-2019-1547: ECDSA remote timing attack

Q: What is the vulnerability ID?

The vulnerability ID is CVE-2019-1547.

Q: What is the severity of CVE-2019-1547?

The severity of CVE-2019-1547 is medium with a severity value of 5.5.

Q: What is the affected software for CVE-2019-1547?

The affected software for CVE-2019-1547 includes jbcs-httpd24-apr, jbcs-httpd24-brotli, jbcs-httpd24-httpd, and jbcs-httpd24-openssl.

Q: How can I fix CVE-2019-1547?

To fix CVE-2019-1547, update to the latest version of the affected software.

Q: Where can I find more information about CVE-2019-1547?

You can find more information about CVE-2019-1547 at the following references: https://arxiv.org/abs/1909.01785, https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=21c856b75d81eff61aa63b4f036bb64a85bf6d46, and https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=30c22fa8b1d840036b8e203585738df62a03cec8.

Published Sep 10, 2019

Updated

ECDSA remote timing attack

Other sources

Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

— Ubuntu

OpenSSL could allow a local authenticated attacker to obtain sensitive information, caused by the ability to construct an EC group missing the cofactor using explicit parameters instead of using a named curve. An attacker could exploit this vulnerability to obtain full key recovery during an ECDSA signature operation.

— IBM

Affected Software

36 affected componentsFixes available

redhat/jbcs-httpd24-apr<0:1.6.3-86.jbcs.el6

0:1.6.3-86.jbcs.el6

redhat/jbcs-httpd24-brotli<0:1.0.6-21.jbcs.el6

0:1.0.6-21.jbcs.el6

redhat/jbcs-httpd24-httpd<0:2.4.37-52.jbcs.el6

0:2.4.37-52.jbcs.el6

redhat/jbcs-httpd24-openssl<1:1.1.1c-16.jbcs.el6

1:1.1.1c-16.jbcs.el6

redhat/jbcs-httpd24-apr<0:1.6.3-86.jbcs.el7

0:1.6.3-86.jbcs.el7

redhat/jbcs-httpd24-brotli<0:1.0.6-21.jbcs.el7

0:1.0.6-21.jbcs.el7

redhat/jbcs-httpd24-httpd<0:2.4.37-52.jbcs.el7

0:2.4.37-52.jbcs.el7

redhat/jbcs-httpd24-openssl<1:1.1.1c-16.jbcs.el7

1:1.1.1c-16.jbcs.el7

redhat/openssl<1:1.1.1c-15.el8

1:1.1.1c-15.el8

OpenSSL OpenSSL>=1.0.2<=1.0.2s

OpenSSL OpenSSL>=1.1.0<=1.1.0k

OpenSSL OpenSSL>=1.1.1<=1.1.1c

IBM Security Verify Governance<=10.0

debian/openssl

3.0.20-1~deb12u23.0.22-1~deb12u23.5.7-1~deb13u23.5.7-1~deb13u33.6.5-1

alpine/openssl>=1.0.2<1.1.1d-r0

1.1.1d-r0