Skip to content

Commit faffcc5

Browse files
committed
doc: provide info on impact of recent vulns
1 parent 85673cc commit faffcc5

File tree

3 files changed

+26
-2
lines changed

3 files changed

+26
-2
lines changed

build.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -270,7 +270,7 @@ function getSource (callback) {
270270
},
271271
banner: {
272272
visible: true,
273-
link: 'https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/'
273+
link: 'https://nodejs.org/en/blog/vulnerability/jan-2018-spectre-meltdown/'
274274
}
275275
}
276276
}

locale/ca/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: index.hbs
33
labels:
4-
banner: Important security releases, please update now!
4+
banner: Spectre and Meltdown in the context of Node.js - no current action required.
55
current-version: Versió actual
66
download: Descarregar
77
download-for: Descarregar per
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
date: 2018-01-08T17:30:00.617Z
3+
category: vulnerability
4+
title: Meltdown and Spectre - Impact On Node.js
5+
slug: jan-2018-spectre-meltdown
6+
layout: blog-post.hbs
7+
author: Michael Dawson
8+
---
9+
10+
# Summary
11+
12+
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.
13+
14+
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.
15+
16+
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.
17+
18+
# Contact and future updates
19+
20+
The current Node.js security policy can be found at https://nodejs.org/en/security/.
21+
22+
Please contact [email protected] if you wish to report a vulnerability in Node.js.
23+
24+
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 commit comments

Comments
 (0)