# CVE-2017-3732: BN_mod_exp may produce incorrect results on x86_64

> A carry propagation bug in OpenSSL's x86_64 Montgomery squaring may allow attackers to deduce private key information from Diffie-Hellman operations.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 May 2017
- **Updated:** 16 Sep 2024
- **Also known as:** ALPINE-CVE-2017-3732, DEBIAN-CVE-2017-3732, GHSA-5hg3-8gvm-5294, UBUNTU-CVE-2017-3732

## What is CVE-2017-3732?

CVE-2017-3732 is a medium-severity vulnerability in Nodejs Node.js, published on 4 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-3732?

It affects 2 products.


Products: Nodejs Node.js, Openssl Openssl.

## How do I fix CVE-2017-3732?

Upgrade to a fixed version.

## Is CVE-2017-3732 being exploited?

There is no known exploitation of CVE-2017-3732 in the wild and no public exploit code.

## Other vulnerabilities in Nodejs Node.js

- [CVE-2023-32002](https://insights.sbomify.com/CVE-2023-32002/): Security feature bypass in Node (critical 9.8)
- [CVE-2016-6303](https://insights.sbomify.com/CVE-2016-6303/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-15896](https://insights.sbomify.com/CVE-2017-15896/): Security feature bypass in Node.js (critical 9.1)
- [CVE-2018-7160](https://insights.sbomify.com/CVE-2018-7160/): Server-side request forgery in Node.js (high 8.8)
- [CVE-2018-12120](https://insights.sbomify.com/CVE-2018-12120/): Misconfiguration in Node.js (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3732 and fix it if it is affected.

What it is: CVE-2017-3732 is a medium-severity vulnerability in Nodejs Node.js, published on 4 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3732 in the wild and no public exploit code.

Affected product: Nodejs Node.js. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-3732/ (Markdown: https://insights.sbomify.com/CVE-2017-3732/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-3732
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-3732
- OSV: https://osv.dev/vulnerability/CVE-2017-3732

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-3732/
Summaries are generated and may contain mistakes; the official description above is the record.