Skip to content

Commit

Permalink
doc: provide info on impact of recent vulns
Browse files Browse the repository at this point in the history
  • Loading branch information
mhdawson committed Jan 8, 2018
1 parent 85673cc commit faffcc5
Show file tree
Hide file tree
Showing 3 changed files with 26 additions and 2 deletions.
2 changes: 1 addition & 1 deletion build.js
Original file line number Diff line number Diff line change
Expand Up @@ -270,7 +270,7 @@ function getSource (callback) {
},
banner: {
visible: true,
link: 'https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/'
link: 'https://nodejs.org/en/blog/vulnerability/jan-2018-spectre-meltdown/'
}
}
}
Expand Down
2 changes: 1 addition & 1 deletion locale/ca/index.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
layout: index.hbs
labels:
banner: Important security releases, please update now!
banner: Spectre and Meltdown in the context of Node.js - no current action required.
current-version: Versió actual
download: Descarregar
download-for: Descarregar per
Expand Down
24 changes: 24 additions & 0 deletions locale/en/blog/vulnerability/jan-2018-spectre-meltdown
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
---
date: 2018-01-08T17:30:00.617Z
category: vulnerability
title: Meltdown and Spectre - Impact On Node.js
slug: jan-2018-spectre-meltdown
layout: blog-post.hbs
author: Michael Dawson
---

# Summary

Project zero has recently announced some new attacks that have received a lot of attention: https://googleprojectzero.blogspot.ca/2018/01/reading-privileged-memory-with-side.html.

The risk from these attacks to systems running Node.js resides in the systems in which your Node.js applications run, as opposed to the Node.js runtime itself. The trust model for Node.js assumes you are running trusted code and does not provide any separation between code running within the runtime itself. Therefore, untrusted code that would be necessary to execute these attacks in Node.js could already affect the execution of your Node.js applications in ways that are more severe than possible through these new attacks.

This does not mean that you don't need to protect yourself from these new attacks when running Node.js applications. To do so, apply the security patches for your operating system. You do not need to update the Node.js runtime.

# Contact and future updates

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

Please contact [email protected] 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 organisation](https://github.com/nodejs/).

0 comments on commit faffcc5

Please sign in to comment.