# CVE-2017-3731: Truncated packet could crash via OOB read

> A truncated packet can cause an out-of-bounds read and crash in OpenSSL on 32-bit hosts using specific ciphers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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-3731, DEBIAN-CVE-2017-3731, GHSA-3cp9-4w64-73cg, UBUNTU-CVE-2017-3731

## What is CVE-2017-3731?

CVE-2017-3731 is a high-severity memory corruption 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

If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d. For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 2 products.


Products: Nodejs Node.js, Openssl Openssl.

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

Upgrade to a fixed version.

## Is CVE-2017-3731 being exploited?

There is no known exploitation of CVE-2017-3731 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-3731 and fix it if it is affected.

What it is: CVE-2017-3731 is a high-severity memory corruption 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-3731 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-3731/ (Markdown: https://insights.sbomify.com/CVE-2017-3731/index.md)
```

## Sources

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

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