Timing side-channel in ECDSA signature computation
Noroxi assessment
Priority: Monitor (action score 16/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.61% (FIRST EPSS).
- Physical access to the device is required. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: OpenSSL OpenSSL 3.0.16, 3.1.8, 3.2.4.
Low priority for now. Upgrade to OpenSSL OpenSSL 3.0.16, 3.1.8, 3.2.4 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
Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency. There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue.
- BDU:2025-03280
- ALSA-2025:15699
- ALSA-2025:16046
- DLA-4176-1
- openSUSE-SU-2025:14696-1
- RLSA-2025:15699
- SUSE-SU-2025:02042-1
- SUSE-SU-2025:0345-1
- SUSE-SU-2025:0349-1
- SUSE-SU-2025:0356-1
- SUSE-SU-2025:0387-1
- SUSE-SU-2025:0388-1
- SUSE-SU-2025:0390-1
- SUSE-SU-2025:0430-1
- SUSE-SU-2025:0613-1
- SUSE-SU-2025:0613-2
- SUSE-SU-2025:0613-3
- SUSE-SU-2025:20233-1
- SUSE-SU-2025:20406-1
- SUSE-SU-2025:20464-1
- Published
- Jan 20, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 48th percentile
- CWE
- CWE-385
Report tools
Action score
16
Monitor
Low priority for now.
- CVSS
- 16 / 40 · 4.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
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
- Proof of concept exists, no weaponized module
- 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.
—
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
- 3.4.0 and later · before 3.4.1affected · semver
- 3.3.0 and later · before 3.3.3affected · semver
- 3.2.0 and later · before 3.2.4affected · semver
- 3.1.0 and later · before 3.1.8affected · semver
- 3.0.0 and later · before 3.0.16affected · semver
- 1.1.1 and later · before 1.1.1zbaffected
- 1.0.2 and later · before 1.0.2zlaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | mysql-selinux | before 1.0.14-1.el10_0 | 1.0.14-1.el10_0 |
| AlmaLinux:10 | mysql8.4-common | before 8.4.6-2.el10_0 | 8.4.6-2.el10_0 |
| AlmaLinux:10 | mysql8.4-errmsg | before 8.4.6-2.el10_0 | 8.4.6-2.el10_0 |
| AlmaLinux:10 | mysql8.4-test-data | before 8.4.6-2.el10_0 | 8.4.6-2.el10_0 |
| AlmaLinux:9 | mecab | before 0.996-3.module_el9.6.0+152+8cbce00c.4 | 0.996-3.module_el9.6.0+152+8cbce00c.4 |
| AlmaLinux:9 | mecab-devel | before 0.996-3.module_el9.6.0+152+8cbce00c.4 | 0.996-3.module_el9.6.0+152+8cbce00c.4 |
| AlmaLinux:9 | mecab-ipadic | before 2.7.0.20070801-24.module_el9.6.0+152+8cbce00c | 2.7.0.20070801-24.module_el9.6.0+152+8cbce00c |
| AlmaLinux:9 | mecab-ipadic-EUCJP | before 2.7.0.20070801-24.module_el9.6.0+152+8cbce00c | 2.7.0.20070801-24.module_el9.6.0+152+8cbce00c |
| AlmaLinux:9 | mysql | before 8.4.6-1.module_el9.6.0+180+a4e757e5 | 8.4.6-1.module_el9.6.0+180+a4e757e5 |
| AlmaLinux:9 | mysql-common | before 8.4.6-1.module_el9.6.0+180+a4e757e5 | 8.4.6-1.module_el9.6.0+180+a4e757e5 |
| AlmaLinux:9 | mysql-devel | before 8.4.6-1.module_el9.6.0+180+a4e757e5 | 8.4.6-1.module_el9.6.0+180+a4e757e5 |
| AlmaLinux:9 | mysql-errmsg | before 8.4.6-1.module_el9.6.0+180+a4e757e5 | 8.4.6-1.module_el9.6.0+180+a4e757e5 |
| AlmaLinux:9 | mysql-libs | before 8.4.6-1.module_el9.6.0+180+a4e757e5 | 8.4.6-1.module_el9.6.0+180+a4e757e5 |
| AlmaLinux:9 | mysql-server | before 8.4.6-1.module_el9.6.0+180+a4e757e5 | 8.4.6-1.module_el9.6.0+180+a4e757e5 |
| AlmaLinux:9 | mysql-test | before 8.4.6-1.module_el9.6.0+180+a4e757e5 | 8.4.6-1.module_el9.6.0+180+a4e757e5 |
| AlmaLinux:9 | mysql-test-data | before 8.4.6-1.module_el9.6.0+180+a4e757e5 | 8.4.6-1.module_el9.6.0+180+a4e757e5 |
| AlmaLinux:9 | rapidjson-devel | before 1.1.0-19.module_el9.6.0+152+8cbce00c | 1.1.0-19.module_el9.6.0+152+8cbce00c |
| AlmaLinux:9 | rapidjson-doc | before 1.1.0-19.module_el9.6.0+152+8cbce00c | 1.1.0-19.module_el9.6.0+152+8cbce00c |
| Alpine:v3.17 | openssl | before 3.0.19-r0 | 3.0.19-r0 |
| Alpine:v3.18 | openssl | before 3.1.8-r0 | 3.1.8-r0 |
| Alpine:v3.20 | openssl | before 3.3.2-r2 | 3.3.2-r2 |
| Alpine:v3.21 | openssl | before 3.3.2-r5 | 3.3.2-r5 |
| Debian:11 | openssl | before 1.1.1w-0+deb11u3 | 1.1.1w-0+deb11u3 |
| Debian:12 | edk2 | all versions | — |
+24
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 |
|---|---|---|
| OpenSSL OpenSSL | 3.0.16 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.1.8 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.2.4 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.3.3 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.4.1 | Vendor (CNA) |
| almalinux:mecab | 0.996-3.module_el9.6.0+152+8cbce00c.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:mecab-devel | 0.996-3.module_el9.6.0+152+8cbce00c.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:mecab-ipadic | 2.7.0.20070801-24.module_el9.6.0+152+8cbce00c · AlmaLinux:9 | Package registry (OSV) |
| almalinux:mecab-ipadic-EUCJP | 2.7.0.20070801-24.module_el9.6.0+152+8cbce00c · AlmaLinux:9 | Package registry (OSV) |
| almalinux:mysql | 8.4.6-1.module_el9.6.0+180+a4e757e5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:mysql-common | 8.4.6-1.module_el9.6.0+180+a4e757e5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:mysql-devel | 8.4.6-1.module_el9.6.0+180+a4e757e5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:mysql-errmsg | 8.4.6-1.module_el9.6.0+180+a4e757e5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:mysql-selinux | 1.0.14-1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:mysql8.4-common | 8.4.6-2.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:mysql8.4-errmsg | 8.4.6-2.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:mysql8.4-test-data | 8.4.6-2.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| alpine:openssl | 3.0.19-r0 · Alpine:v3.17 | Package registry (OSV) |
| debian:edk2 | 2025.02-8+deb13u1 · Debian:13 | Package registry (OSV) |
| debian:openssl | 3.0.16-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:openssl-1_1 | 1.1.1w-150600.5.12.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:openssl-3 | 3.1.4-150600.5.24.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| rocky linux:mysql-selinux | 0:1.0.14-1.el10_0 · Rocky Linux:10 | Package registry (OSV) |
| rocky linux:mysql8.4 | 0:8.4.6-2.el10_0 · Rocky Linux:10 | Package registry (OSV) |
| suse:nodejs24 | 24.18.1-150700.15.18.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP7 | Package registry (OSV) |
| suse:openssl | 3.5.0-150700.3.4.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:openssl-1_1 | 1.1.1l-150500.17.40.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:openssl-1_1 | 1.1.1w-150600.5.12.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:openssl-3 | 3.1.4-150600.5.24.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:openssl-3 | 3.2.3-150700.5.5.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-08-19 |
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.
- Published
- First PoC+576 d
- TodayOct 13, 2026+631 d
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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- George Pantelakis (Red Hat)finder
- Alicja Kario (Red Hat)finder
- Tomáš Mrázremediation developer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-9231253 days apartTiming side-channel in SM2 algorithm on 64 bit ARM27Monitor
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).
Technical details
Attack conditions
- Physical access to the device is required.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-385 · Covert Timing ChannelCVSS vector
CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (12 more)Show less
- github.com/openssl/openssl/commit/2af62e74fb59bc469506bc37eb2990ea408d9467
- github.com/openssl/openssl/commit/392dcb336405a0c94486aa6655057f59fd3a0902
- github.com/openssl/openssl/commit/4b1cb94a734a7d4ec363ac0a215a25c181e11f65
- github.com/openssl/openssl/commit/77c608f4c8857e63e98e66444e2e761c9627916f
- github.openssl.org/openssl/extended-releases/commit/0d5fd1ab987f7571e2c955d8d8b638fc0fb54ded
- github.openssl.org/openssl/extended-releases/commit/a2639000db19878d5d89586ae7b725080592ae86
- openssl-library.org/news/secadv/20250120.txt
- www.openwall.com/lists/oss-security/2025/01/20/2
- lists.debian.org/debian-lts-announce/2025/05/msg00028.html
- security.netapp.com/advisory/ntap-20250124-0005/
- security.netapp.com/advisory/ntap-20250418-0010/
- security.netapp.com/advisory/ntap-20250502-0006/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.