CVE-2017-3732
BN_mod_exp may produce incorrect results on x86_64
Reported by openssl · Published May 4, 2017
There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL 1.0.2 before 1.0.2k and 1.1.0 before 1.1.0d. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. For example this can occur by default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very similar to CVE-2015-3193 but must be treated as a separate problem.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| lib32-openssl | Arch Linux | 1:1.0.2.k-1 |
| node.js | nodejs | 7.5.0, 6.9.5, 6.8.1, 5.12.0, 4.7.3, 4.1.2 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| OpenSSL | OpenSSL | openssl-1.1.0, openssl-1.1.0a, openssl-1.1.0b |
| arch | lib32-openssl | 0 |
| OpenSSL | OpenSSL | 1.1.0, 1.0.2 |
| OpenSSL | OpenSSL | |
| arch | openssl | 0 |
| alpine | openssl | 0 |
Timeline
- Jan 26, 2017 CVE Published
- Oct 2, 2020 PoC Published (7 in total, the first dated here)
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Jun 2, 2025 CVE Updated
- Mar 6, 2026 Distribution Patch (10 in total, the first dated here)
- Mar 6, 2026 Security Advisory (14 in total, the first dated here)
- Sep 29, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2017-3732
vulnetix vdb fixes CVE-2017-3732
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-2017-3732/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- RHSA-2018:2185 vendor-advisoryx_refsource_REDHAT
- RHSA-2018:2186 vendor-advisoryx_refsource_REDHAT
- x_refsource_CONFIRM
- RHSA-2018:2713 vendor-advisoryx_refsource_REDHAT
- x_refsource_MISC
- FreeBSD-SA-17:02 vendor-advisoryx_refsource_FREEBSD
- x_refsource_CONFIRM
- 1037717 vdb-entryx_refsource_SECTRACK
- RHSA-2018:2575 vendor-advisoryx_refsource_REDHAT
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- GLSA-201702-07 vendor-advisoryx_refsource_GENTOO
- RHSA-2018:2568 vendor-advisoryx_refsource_REDHAT
- 95814 vdb-entryx_refsource_BID
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- RHSA-2018:2187 vendor-advisoryx_refsource_REDHAT
- x_refsource_MISC