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).
Conclusion & alert: CVE-2019-1547 is rated Moderate Risk (42.1/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.20%). Mandatory action: Review affected assets and schedule remediation.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
| # | Date | Old EPSS score | New EPSS score | Delta (New - Old) |
|---|---|---|---|---|
| 1 | 2026-06-15 | 0.26% | 1.20% | +0.94% |
| 2 | 2025-12-28 | 0.23% | 0.26% | +0.03% |
| 3 | 2025-12-27 | — | 0.23% | — |
Full EPSS history (19 records total)
CVSS metrics for this CVE.
| Base score | Version | Severity | Vector | Exploitability | Impact | Score source |
|---|---|---|---|---|---|---|
| 4.7 | 3.1 | MEDIUM |
|
1.0 | 3.6 | [email protected] |
| 1.9 | 2.0 | LOW |
|
3.4 | 2.9 | [email protected] |
| vendor | priority | summary | link |
|---|---|---|---|
alpine
|
medium | CVE-2019-1547: 3 source package rows (openssl, openssl1.1-compat, openssl3); 15 state rows across 13 repos (3.10-main, 3.11-main, 3.12-main, 3.17-community, 3.17-main, 3.18-community, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-community, edge-main); fixed 15, open 0. | https://security.alpinelinux.org/vuln/CVE-2019-1547 |
debian
|
not yet assigned | CVE-2019-1547 not yet assigned priority: Debian including 1 source packages (openssl), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. | https://security-tracker.debian.org/tracker/CVE-2019-1547 |
gentoo
|
low | CVE-2019-1547: 1 GLSA(s) (201911-04), 1 atom(s) (dev-libs/openssl); latest impact low. | https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2019-1547 |
redhat
|
medium | — | https://access.redhat.com/security/cve/CVE-2019-1547 |
suse
|
medium | CVE-2019-1547 severity moderate: SUSE including 490 source package names (0.1.0:libopenssl1_1-1.1.0i-14.3.1, 0.1.75:libopenssl1_1-1.1.0i-14.3.1, …), 873 product×package rows across 169 product lines (Container caasp/v4/389-ds, Container caasp/v4/busybox, … (169 product lines)): Fixed 677, Known Affected 157, Known Not Affected 39. | https://www.suse.com/security/cve/CVE-2019-1547/ |
ubuntu
|
low | CVE-2019-1547 low priority: Ubuntu including 4 source packages (edk2, nodejs, openssl, openssl1.0), 28 status rows across 7 suites (bionic, disco, eoan, focal, trusty, upstream, xenial): not-affected 11, released 7, DNE 6, needs-triage 3, ignored 1. | https://ubuntu.com/security/CVE-2019-1547 |