Skip to content

blog: sep 2019 security no-release announcement #2572

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 12, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 46 additions & 0 deletions locale/en/blog/vulnerability/september-2019-openssl-no-updates.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
date: 2019-09-12T17:00:15.000Z
category: vulnerability
title: OpenSSL security releases do not require Node.js security releases
slug: openssl-fixes-unneeded-sep-2019
layout: blog-post.hbs
author: Sam Roberts
---

### Summary

The OpenSSL Security releases of September 10th, 2019 do not affect Node.js.

### Analysis

Our assessment of the [security advisory](https://www.openssl.org/news/secadv/20190910.txt) is:

- ECDSA remote timing attack (CVE-2019-1547)
Not affected. Node supports only named curves for ECDSA signing.

- Fork Protection (CVE-2019-1549)
Not affected. Node.js always call `exec()` after `fork()` so will not the
duplicate PRNG state in the forked process.

- Padding Oracle in `PKCS7_dataDecode` and `CMS_decrypt_set1_pkey` (CVE-2019-1563)
Not affected. Node does not support PCKS7 and CMS.

Given this assessment, the OpenSSL updates will be treated as non-security
patch updates, and will come out in the regularly scheduled updates to
supported release lines.

### Acknowledgements

Thanks to [Shigeki Ohtsu](https://github.com/shigeki) for his rapid analysis
of the OpenSSL security advisory.

### Contact and future updates

The current Node.js security policy can be found at <https://nodejs.org/en/security/>,
including information on how to report a vulnerability in Node.js.

Subscribe to the low-volume announcement-only **nodejs-sec** mailing list at
https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on
security vulnerabilities and security-related releases of Node.js and the
projects maintained in the
[nodejs GitHub organisation](https://github.com/nodejs).