CVE-2019-1547
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.
| Package | Ecosystem | Fixed in |
|---|---|---|
| openssl-devel | Amazon Linux | 1:1.0.2k-19.amzn2.0.3 |
| openssl11-static | Amazon Linux | 1:1.1.1c-15.amzn2.0.1 |
| openssl11-libs | Amazon Linux | 1:1.1.1c-15.amzn2.0.1 |
| openssl | Amazon Linux | 1:1.0.2k-19.amzn2.0.3 |
| openssl3 | Alpine | 1.1.1d-r1 |
| openssl11 | Amazon Linux | 1:1.1.1c-15.amzn2.0.1 |
| openssl-static | Amazon Linux | 1:1.0.2k-19.amzn2.0.3 |
| openssl-perl | Amazon Linux | 1:1.0.2k-19.amzn2.0.3 |
| openssl11-devel | Amazon Linux | 1:1.1.1c-15.amzn2.0.1 |
| openssl | openssl | 1.1.1c, 1.1.0k, 1.0.2s |
| openssl | Ubuntu:Pro:14.04:LTS | 1.0.1f-1ubuntu2.27+esm1 |
| openssl | Ubuntu:18.04:LTS | 1.1.1-1ubuntu2.1~18.04.6 |
2 more packages have a fixed version. See every fix in Lookup.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| OpenSSL | OpenSSL | 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) |
| amazon:2 | openssl-devel | 0 |
| amazon:2 | openssl11-static | 0 |
| amazon:2 | openssl11-libs | 0 |
| amazon:2 | openssl | 0 |
| alpine | openssl3 | 0 |
| amazon:2 | openssl11 | 0 |
| amazon:2 | openssl-static | 0 |
| amazon:2 | openssl-perl | 0 |
| amazon:2 | openssl11-devel | 0 |
| OpenSSL | OpenSSL | 1.1.1, 1.1.0, 1.0.2 |
| amazon:2 | openssl-libs | 0 |
| alpine | openssl | 0, 0, 0 |
| alpine | openssl1.1-compat | 0 |
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
References
- 20190912 [slackware-security] openssl (SSA:2019-254-03) mailing-list
- openSUSE-SU-2019:2158 vendor-advisory
- FEDORA-2019-d15aac6c4e vendor-advisory
- openSUSE-SU-2019:2189 vendor-advisory
- [debian-lts-announce] 20190925 [SECURITY] [DLA 1932-1] openssl security update mailing-list
- FEDORA-2019-d51641f152 vendor-advisory
- 20191001 [SECURITY] [DSA 4539-1] openssl security update mailing-list
- 20191001 [SECURITY] [DSA 4540-1] openssl1.0 security update mailing-list
- DSA-4539 vendor-advisory
- DSA-4540 vendor-advisory
- openSUSE-SU-2019:2268 vendor-advisory
- openSUSE-SU-2019:2269 vendor-advisory
- GLSA-201911-04 vendor-advisory
- USN-4376-1 vendor-advisory
…and 15 more