ECDSA remote timing attack
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 66.8% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: openssl (Alpine:v3.10) 1.1.1d-r0; openssl (Alpine:v3.11) 1.1.1d-r1; openssl3 (Alpine:v3.15) 1.1.1d-r1.
- Mentioned 4 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to openssl (Alpine:v3.10) 1.1.1d-r0; openssl (Alpine:v3.11) 1.1.1d-r1; openssl3 (Alpine:v3.15) 1.1.1d-r1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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).
- BDU:2019-04084
- DLA-1932-1
- DSA-4539-1
- DSA-4540-1
- openSUSE-SU-2019:2158-1
- openSUSE-SU-2019:2189-1
- openSUSE-SU-2019:2268-1
- openSUSE-SU-2019:2269-1
- RHSA-2020:1337
- RHSA-2020:1840
- SUSE-SU-2019:14171-1
- SUSE-SU-2019:14174-1
- SUSE-SU-2019:2397-1
- SUSE-SU-2019:2403-1
- SUSE-SU-2019:2410-1
- SUSE-SU-2019:2413-1
- SUSE-SU-2019:2504-1
- SUSE-SU-2019:2558-1
- SUSE-SU-2019:2561-1
- SUSE-SU-2020:0099-1
- Published
- Sep 10, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.2% · 67th percentile
- CWE
- —
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openssl openssl1.0.2 and later · up to 1.0.2s inclusive
- openssl openssl1.1.0 and later · up to 1.1.0k inclusive
- openssl openssl1.1.1 and later · up to 1.1.1c inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
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)affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | openssl | from 1.0.2 · before 1.1.1d-r0 | 1.1.1d-r0 |
| Alpine:v3.11 | openssl | from 1.0.2 · before 1.1.1d-r1 | 1.1.1d-r1 |
| Alpine:v3.15 | openssl3 | before 1.1.1d-r1 | 1.1.1d-r1 |
| Alpine:v3.7 | openssl | from 1.0.2 · before 1.0.2t-r0 | 1.0.2t-r0 |
| Debian:10 | openssl | before 1.1.1d-0+deb10u1 | 1.1.1d-0+deb10u1 |
| Debian:12 | openssl | before 1.1.1d-1 | 1.1.1d-1 |
| Debian:8 | openssl | before 1.0.1t-1+deb8u12 | 1.0.1t-1+deb8u12 |
| Debian:9 | openssl | before 1.1.0l-1~deb9u1 | 1.1.0l-1~deb9u1 |
| Debian:9 | openssl1.0 | before 1.0.2t-1~deb9u1 | 1.0.2t-1~deb9u1 |
| openSUSE:Leap 15.0 | openssl-1_0_0 | before 1.0.2p-lp150.2.19.1 | 1.0.2p-lp150.2.19.1 |
| openSUSE:Leap 15.0 | openssl-1_1 | before 1.1.0i-lp150.3.25.1 | 1.1.0i-lp150.3.25.1 |
| openSUSE:Leap 15.1 | openssl-1_0_0 | before 1.0.2p-lp151.5.10.1 | 1.0.2p-lp151.5.10.1 |
| openSUSE:Leap 15.1 | openssl-1_1 | before 1.1.0i-lp151.8.3.1 | 1.1.0i-lp151.8.3.1 |
| Red Hat:enterprise_linux:8::baseos | openssl | before 1:1.1.1c-15.el8 | 1:1.1.1c-15.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-debuginfo | before 1:1.1.1c-15.el8 | 1:1.1.1c-15.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-debugsource | before 1:1.1.1c-15.el8 | 1:1.1.1c-15.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-devel | before 1:1.1.1c-15.el8 | 1:1.1.1c-15.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-libs | before 1:1.1.1c-15.el8 | 1:1.1.1c-15.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-libs-debuginfo | before 1:1.1.1c-15.el8 | 1:1.1.1c-15.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-perl | before 1:1.1.1c-15.el8 | 1:1.1.1c-15.el8 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apr | before 0:1.6.3-86.jbcs.el6 | 0:1.6.3-86.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apr-debuginfo | before 0:1.6.3-86.jbcs.el6 | 0:1.6.3-86.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apr-devel | before 0:1.6.3-86.jbcs.el6 | 0:1.6.3-86.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-brotli | before 0:1.0.6-21.jbcs.el6 | 0:1.0.6-21.jbcs.el6 |
+58
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code 65This week
- CVE-2016-2108The ASN.1 implementation in OpenSSL before 1.0.1o and 1.0.2 before 1.0.2c allows remote attackers to execute arbitrary code or cause a denia62This week
- CVE-2016-6309statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a den60This week
- CVE-2022-3786X.509 Email Address Variable Length Buffer Overflow58Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:openssl | 1.1.1d-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:openssl3 | 1.1.1d-r1 · Alpine:v3.15 | Package registry (OSV) |
| debian:openssl | 1.1.1d-1 · Debian:12 | Package registry (OSV) |
| debian:openssl1.0 | 1.0.2t-1~deb9u1 · Debian:9 | Package registry (OSV) |
| opensuse:openssl-1_0_0 | 1.0.2p-lp150.2.19.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| opensuse:openssl-1_1 | 1.1.0i-lp151.8.3.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr | 0:1.6.3-86.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-debuginfo | 0:1.6.3-86.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-devel | 0:1.6.3-86.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-brotli | 0:1.0.6-21.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-brotli-debuginfo | 0:1.0.6-21.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-brotli-devel | 0:1.0.6-21.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd | 0:2.4.37-52.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd-debuginfo | 0:2.4.37-52.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd-devel | 0:2.4.37-52.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd-manual | 0:2.4.37-52.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd-selinux | 0:2.4.37-52.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd-tools | 0:2.4.37-52.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| suse:compat-openssl098 | 0.9.8j-106.15.1 · SUSE:Linux Enterprise Desktop 12 SP4 | Package registry (OSV) |
| suse:openssl | 0.9.8j-0.106.25.1 · SUSE:Linux Enterprise Point of Sale 11 SP3 | Package registry (OSV) |
| suse:openssl-1_0_0 | 1.0.2p-3.11.1 · SUSE:Linux Enterprise Desktop 12 SP4 | Package registry (OSV) |
| suse:openssl-1_1 | 1.1.0i-14.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP1 | Package registry (OSV) |
| suse:openssl1 | 1.0.1g-0.58.21.1 · SUSE:Linux Enterprise Server 11-SECURITY | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0964 · Dec 3, 2021(Hitachi Güvenlik Zafiyeti)
- TR-21-0427 · May 31, 2021(IBM Güvenlik Bülteni Yayınladı)
- TR-20-905 · Oct 30, 2020(OpenShift Güvenlik Güncellemesi)
- TR-20-794 · Sep 30, 2020(IBM Event Streams Güvenlik Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- lists.opensuse.org/opensuse-security-announce/2019-09/msg00072.html
- lists.opensuse.org/opensuse-security-announce/2019-10/msg00012.html
- lists.opensuse.org/opensuse-security-announce/2019-10/msg00016.html
- packetstormsecurity.com/files/154467/Slackware-Security-Advisory-openssl-Updates.html
- arxiv.org/abs/1909.01785
- git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=21c856b75d81eff61aa63b4f036bb64a85bf6d46
- git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=30c22fa8b1d840036b8e203585738df62a03cec8
- git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=7c1709c2da5414f5b6133d00a03fc8c5bf996c7a
- kc.mcafee.com/corporate/index?page=content&id=SB10365
- lists.debian.org/debian-lts-announce/2019/09/msg00026.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GY6SNRJP2S7Y42GIIDO3HXPNMDYN2U3A/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZN4VVQJ3JDCHGIHV4Y2YTXBYQZ6PWQ7E/
- seclists.org/bugtraq/2019/Oct/0
- seclists.org/bugtraq/2019/Oct/1
- seclists.org/bugtraq/2019/Sep/25
- security.gentoo.org/glsa/201911-04
- security.netapp.com/advisory/ntap-20190919-0002/
- security.netapp.com/advisory/ntap-20200122-0002/
- security.netapp.com/advisory/ntap-20200416-0003/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.