VDB

CVE-2019-1547

CVE-2019-1547 PUBLISHED

ECDSA remote timing attack

Reported by openssl · Published September 10, 2019

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).

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
openssl-develAmazon Linux1:1.0.2k-19.amzn2.0.3
openssl11-staticAmazon Linux1:1.1.1c-15.amzn2.0.1
openssl11-libsAmazon Linux1:1.1.1c-15.amzn2.0.1
opensslAmazon Linux1:1.0.2k-19.amzn2.0.3
openssl3Alpine1.1.1d-r1
openssl11Amazon Linux1:1.1.1c-15.amzn2.0.1
openssl-staticAmazon Linux1:1.0.2k-19.amzn2.0.3
openssl-perlAmazon Linux1:1.0.2k-19.amzn2.0.3
openssl11-develAmazon Linux1:1.1.1c-15.amzn2.0.1
opensslopenssl1.1.1c, 1.1.0k, 1.0.2s
opensslUbuntu:Pro:14.04:LTS1.0.1f-1ubuntu2.27+esm1
opensslUbuntu:18.04:LTS1.1.1-1ubuntu2.1~18.04.6

2 more packages have a fixed version. See every fix in Lookup.

Affected products

VendorProductVersions
OpenSSLOpenSSLFixed 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)
amazon:2openssl-devel0
amazon:2openssl11-static0
amazon:2openssl11-libs0
amazon:2openssl0
alpineopenssl30
amazon:2openssl110
amazon:2openssl-static0
amazon:2openssl-perl0
amazon:2openssl11-devel0
OpenSSLOpenSSL1.1.1, 1.1.0, 1.0.2
amazon:2openssl-libs0
alpineopenssl0, 0, 0
alpineopenssl1.1-compat0

Timeline

  • Sep 10, 2019 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Nov 21, 2024 CVE Updated
  • Mar 6, 2026 Distribution Patch (48 in total, the first dated here)
  • Mar 6, 2026 Security Advisory (61 in total, the first dated here)
  • Sep 14, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2019-1547
vulnetix vdb fixes CVE-2019-1547

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2019-1547/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›