Skip to content

Commit 070cd26

Browse files
mhdawsonfhemberger
authored andcommitted
doc: june 2018 sec pre-announce (#1680)
Add blog for June 2018 pre-announce Update header to point to pre-announce
1 parent aee97da commit 070cd26

File tree

2 files changed

+35
-3
lines changed

2 files changed

+35
-3
lines changed

build.js

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -254,9 +254,9 @@ function getSource (callback) {
254254
lts: latestVersion.lts(versions)
255255
},
256256
banner: {
257-
visible: false,
258-
text: 'Important March 2018 security upgrades now available',
259-
link: '/en/blog/vulnerability/march-2018-security-releases/'
257+
visible: true,
258+
text: 'June 2018 Security Releases',
259+
link: '/en/blog/vulnerability/june-2018-security-releases/'
260260
}
261261
}
262262
}
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
date: 2018-06-06T03:18:59.230Z
3+
category: vulnerability
4+
title: June 2018 Security Releases
5+
slug: june-2018-security-releases
6+
layout: blog-post.hbs
7+
author: Michael Dawson
8+
---
9+
10+
# Summary
11+
12+
Node.js will release new versions of all supported release lines on or around June 12th, 2018 (UTC). These releases will incorporate a number of security fixes.
13+
14+
# Impact
15+
16+
* All versions of Node.js 6.x (LTS "Boron") are vulnerable to 1 denial-of-service (DoS) vulnerability with a severity of LOW.
17+
* All versions of Node.js 8.x (LTS "Carbon") are vulnerable to 2 denial-of-service (DoS) vulnerabilities, the highest severity being HIGH.
18+
* Versions of Node.js 9.x are vulnerable to 5 denial-of-service (DoS) vulnerabilities, the highest severity being HIGH.
19+
* All versions of Node.js 10.x (Current) are vulnerable to 4 denial-of-service (DoS) vulnerabilities, the highest severity being HIGH.
20+
21+
# Release timing
22+
23+
Releases will be available on or around June 12th, 2018 (UTC), along with disclosure of the details for the flaws addressed in each release in order to allow for complete impact assessment by users.
24+
25+
# Contact and future updates
26+
27+
The current Node.js security policy can be found at https://nodejs.org/en/security/.
28+
29+
Please contact [email protected] if you wish to report a vulnerability in Node.js.
30+
31+
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](https://github.com/nodejs/).
32+

0 commit comments

Comments
 (0)