Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign updeps: float two (more) OpenSSL patches for DSA vulnerabilities #23965
Conversation
rvagg
added some commits
Oct 30, 2018
This comment has been minimized.
This comment has been minimized.
nodejs-github-bot
added
the
openssl
label
Oct 30, 2018
rvagg
referenced this pull request
Oct 30, 2018
Closed
deps: float 99540ec from openssl (CVE-2018-0735) #23950
ryzokuken
approved these changes
Oct 30, 2018
tniessen
approved these changes
Oct 30, 2018
fhinkel
approved these changes
Oct 30, 2018
jasnell
approved these changes
Oct 30, 2018
targos
added this to Backport requested
in v11.x
Nov 1, 2018
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Landed in c1e6703...213c7d2 |
Trott
closed this
Nov 4, 2018
Trott
added a commit
to Trott/io.js
that referenced
this pull request
Nov 4, 2018
Trott
added a commit
to Trott/io.js
that referenced
this pull request
Nov 4, 2018
rvagg
deleted the
rvagg:rvagg/openssl-CVE-2018-0734
branch
Nov 6, 2018
rvagg
added a commit
to rvagg/io.js
that referenced
this pull request
Nov 14, 2018
rvagg
added a commit
to rvagg/io.js
that referenced
this pull request
Nov 14, 2018
rvagg
referenced this pull request
Nov 14, 2018
Closed
OpenSSL float backports for 8.x and 6.x #24354
BridgeAR
removed
backport-requested-v10.x
backport-requested-v11.x
labels
Nov 14, 2018
BridgeAR
added a commit
that referenced
this pull request
Nov 14, 2018
BridgeAR
added a commit
that referenced
this pull request
Nov 14, 2018
targos
added
the
dont-land-on-v11.x
label
Nov 18, 2018
This comment has been minimized.
This comment has been minimized.
|
@rvagg IIUC this will be part of the next OpenSSL release, so I'm adding the dont-land-on label. Please correct me if I'm wrong. |
targos
removed this from Backport requested
in v11.x
Nov 18, 2018
targos
added this to Don't land (ever)
in v11.x
Nov 18, 2018
This was referenced Apr 23, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
rvagg commentedOct 30, 2018
Build on from #23950 we have two more issues surrounding DSA.
One has a CVE, CVE-2018-0734 @ https://www.openssl.org/news/secadv/20181030.txt
The other runs into OpenSSL's severity-level policy for CVE assignment and doesn't quite make it so we don't have a CVE for it. openssl/openssl#7487
If this is accepted I'll put in a PR for 6 & 8 since they have different patches (for 1.0.2).
FWIW I don't believe any of these rise to much of a meaningful level of severity. We're seeing an expected wave of timing attack vulnerabilities being discovered because this is the hottest area for research right now (for good reason, it's fascinating!). But a lot of them are more academic in nature in that they require very specific circumstances to be able to build a successful attack. And in these cases I don't believe exploits have been published anywhere.
Still worth floating on our releases I reckon though. Erring on the side of security is what the vast majority of our users want to see us do.
/cc @nodejs/crypto @nodejs/security