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

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

Which versions are affected by CVE-2017-3731?

It affects 2 products.

Products include Nodejs Node.js, Openssl Openssl.

How do I fix CVE-2017-3731?

Upgrade to a fixed version.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

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 Security feature bypass in Node Critical 9.8
• CVE-2016-6303 Integer overflow in n/a Critical 9.8
• CVE-2017-15896 Security feature bypass in Node.js Critical 9.1
• CVE-2018-7160 Server-side request forgery in Node.js High 8.8
• CVE-2018-12120 Misconfiguration in Node.js High 8.1

All Nodejs Node.js vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as ALPINE-CVE-2017-3731, DEBIAN-CVE-2017-3731, GHSA-3cp9-4w64-73cg, UBUNTU-CVE-2017-3731.