Skip to content
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

blog: add blog for dec security releases #2822

Merged
merged 2 commits into from
Dec 12, 2019
Merged
Show file tree
Hide file tree
Changes from 1 commit
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
6 changes: 3 additions & 3 deletions build.js
Original file line number Diff line number Diff line change
Expand Up @@ -290,9 +290,9 @@ function getSource (callback) {
lts: latestVersion.lts(versions)
},
banner: {
visible: false,
text: 'New security releases now available for all release lines',
link: '/en/blog/vulnerability/february-2019-security-releases/'
visible: true,
text: 'New security releases to be made available Dec 17, 2019',
link: '/en/blog/vulnerability/december-2019-security-releases/'
}
}
}
Expand Down
28 changes: 28 additions & 0 deletions locale/en/blog/vulnerability/december-2019-security-releases.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---
date: 2019-12-12T18:R2047.733Z
mhdawson marked this conversation as resolved.
Show resolved Hide resolved
category: vulnerability
title: December 2019 Security Releases
slug: december-2019-security-releases
layout: blog-post.hbs
author: Michael Dawson
---

# Summary


Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what are those "LSEP" characters?


The Node.js project will release new versions of all supported release lines on or shortly after Tuesday December 17, 2019 UTC. The only update in these releases will be an updated version of npm addressing the vulnerability announced in https://blog.npmjs.org/post/189618601100/binary-planting-with-the-npm-cli.

In the meantime, users should update to npm 6.13.4 by following the instructions provided in the npm advisory. As a general rule, avoid running npm in production environments.

# Impact

All versions of Node.js are vulnerable including the LTS and current releases: Node.js 8 (LTS "Carbon"), Node.js 10 (LTS "Dubnium") , Node.js 12 (LTS "Erbium"), and Node.js 13.

# Release timing


Releases will be available at, or shortly after, Tuesday, December 17, 2019 UTC.

# 
Contact and future updates



The current Node.js security policy can be found at https://nodejs.org/en/security/.

 Please follow the process outlined in https://github.com/nodejs/node/blob/master/SECURITY.md if you wish 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 organization.