-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
doc: provide info on impact of recent vulns #1547
Changes from 3 commits
faffcc5
d56a789
67a7e6a
d4df409
985245e
d9d70d0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
--- | ||
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. If an attacker | ||
manages to run malicious code on an upatched OS (whether using | ||
javascript or something else) they may be able to access memory and or | ||
data that they should not have access to. In order to protect yourself | ||
from these cases, apply the security patches for your operating | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. does it make sense to link to these resources? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @hashseed I'm not sure what all links/patches are available for OS's so far. Maybe that is something we can add in later on. |
||
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/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe "JavaScript" instead of "javascript" here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@matteocontrini pushed commit to fix