Skip to content

deps: upgrade openssl to 1.0.1s - #5508

Merged
bnoordhuis merged 1 commit into
nodejs:v0.10-stagingfrom
bnoordhuis:v0.10-openssl-1.0.1s
Mar 1, 2016
Merged

deps: upgrade openssl to 1.0.1s#5508
bnoordhuis merged 1 commit into
nodejs:v0.10-stagingfrom
bnoordhuis:v0.10-openssl-1.0.1s

Conversation

@bnoordhuis

Copy link
Copy Markdown
Member

@bnoordhuisbnoordhuis added crypto Issues and PRs related to the crypto subsystem. land-on-v0.10 labels Mar 1, 2016
@indutny

Copy link
Copy Markdown
Member

LGTM if CI is green

@shigeki

Copy link
Copy Markdown
Contributor

Are the tests of '--enable-ssl2 still working? I thought we should remove supporting ssl2 at first.

@shigeki

Copy link
Copy Markdown
Contributor

I've just made shigeki@bd65f9c to remove SSLv2 support on v0.12 but not run ci yet. It should be discussed on LTS.

@bnoordhuis

Copy link
Copy Markdown
MemberAuthor

It looks like there's no real test coverage for --enable-ssl2, the CI doesn't run the stuff in test/external...

@shigeki

Copy link
Copy Markdown
Contributor

Okay, we can remove SSLv2 support even after upgrading.

@bnoordhuis

Copy link
Copy Markdown
MemberAuthor

Interestingly, I ran test/external/ssl-options/test.js for ~7700 iterations and it didn't fail once, but I suspect that, as tests go, it's self-referential and just not very good. If you start a TLS server with --enable-ssl2 --enable-ssl3, you can't actually connect over SSLv2, only SSLv3.

PR-URL: nodejs#5508
Reviewed-By: Fedor Indutny <fedor@indutny.com>
@bnoordhuis
bnoordhuisforce-pushed the v0.10-openssl-1.0.1s branch from 50d7310 to 42ded2aCompareMarch 1, 2016 19:00
@bnoordhuis
bnoordhuis merged commit 42ded2a into nodejs:v0.10-stagingMar 1, 2016
@bnoordhuis
bnoordhuis deleted the v0.10-openssl-1.0.1s branch March 1, 2016 19:00
@bnoordhuis

Copy link
Copy Markdown
MemberAuthor

Landed in the v0.10-staging branch in 42ded2a.

test/simple/test-http-header-obstext.js consistently times out but that's not caused by this pull request. /cc @jasnell

rvagg added a commit that referenced this pull request Mar 3, 2016
Notable changes:
* http_parser: Update to http-parser 1.2 to fix an unintentionally
strict limitation of allowable header characters.
(James M Snell) #5242
* domains:
- Prevent an exit due to an exception being thrown rather than
emitting an 'uncaughtException' event on the `process` object when
no error handler is set on the domain within which an error is
thrown and an 'uncaughtException' event listener is set on
`process`. (Julien Gilli) #3887
- Fix an issue where the process would not abort in the proper
function call if an error is thrown within a domain with no error
handler and `--abort-on-uncaught-exception` is used.
(Julien Gilli) #3887
* openssl: Upgrade from 1.0.1r to 1.0.1s
(Ben Noordhuis) #5508
- Fix a double-free defect in parsing malformed DSA keys that may
potentially be used for DoS or memory corruption attacks. It is
likely to be very difficult to use this defect for a practical
attack and is therefore considered low severity for Node.js users.
More info is available at
https://www.openssl.org/news/vulnerabilities.html#2016-0705
- Fix a defect that can cause memory corruption in certain very rare
cases relating to the internal `BN_hex2bn()` and `BN_dec2bn()`
functions. It is believed that Node.js is not invoking the code
paths that use these functions so practical attacks via Node.js
using this defect are _unlikely_ to be possible. More info is
available at
https://www.openssl.org/news/vulnerabilities.html#2016-0797
- Fix a defect that makes the CacheBleed Attack
(https://ssrg.nicta.com.au/projects/TS/cachebleed/) possible.
This defect enables attackers to execute side-channel attacks
leading to the potential recovery of entire RSA private keys. It
only affects the Intel Sandy Bridge (and possibly older)
microarchitecture when using hyper-threading. Newer
microarchitectures, including Haswell, are unaffected. More info
is available at
https://www.openssl.org/news/vulnerabilities.html#2016-0702
- Remove SSLv2 support, the `--enable-ssl2` command line argument
will now produce an error. The DROWN Attack
(https://drownattack.com/) creates a vulnerability where SSLv2 is
enabled by a server, even if a client connection is not using
SSLv2. The SSLv2 protocol is widely considered unacceptably broken
and should not be supported. More information is available at
https://www.openssl.org/news/vulnerabilities.html#2016-0800
PR-URL: #5404
rvagg added a commit that referenced this pull request Mar 4, 2016
Notable changes:
* http_parser: Update to http-parser 1.2 to fix an unintentionally
strict limitation of allowable header characters.
(James M Snell) #5242
* domains:
- Prevent an exit due to an exception being thrown rather than
emitting an 'uncaughtException' event on the `process` object when
no error handler is set on the domain within which an error is
thrown and an 'uncaughtException' event listener is set on
`process`. (Julien Gilli) #3887
- Fix an issue where the process would not abort in the proper
function call if an error is thrown within a domain with no error
handler and `--abort-on-uncaught-exception` is used.
(Julien Gilli) #3887
* openssl: Upgrade from 1.0.1r to 1.0.1s
(Ben Noordhuis) #5508
- Fix a double-free defect in parsing malformed DSA keys that may
potentially be used for DoS or memory corruption attacks. It is
likely to be very difficult to use this defect for a practical
attack and is therefore considered low severity for Node.js users.
More info is available at
https://www.openssl.org/news/vulnerabilities.html#2016-0705
- Fix a defect that can cause memory corruption in certain very rare
cases relating to the internal `BN_hex2bn()` and `BN_dec2bn()`
functions. It is believed that Node.js is not invoking the code
paths that use these functions so practical attacks via Node.js
using this defect are _unlikely_ to be possible. More info is
available at
https://www.openssl.org/news/vulnerabilities.html#2016-0797
- Fix a defect that makes the CacheBleed Attack
(https://ssrg.nicta.com.au/projects/TS/cachebleed/) possible.
This defect enables attackers to execute side-channel attacks
leading to the potential recovery of entire RSA private keys. It
only affects the Intel Sandy Bridge (and possibly older)
microarchitecture when using hyper-threading. Newer
microarchitectures, including Haswell, are unaffected. More info
is available at
https://www.openssl.org/news/vulnerabilities.html#2016-0702
- Remove SSLv2 support, the `--enable-ssl2` command line argument
will now produce an error. The DROWN Attack
(https://drownattack.com/) creates a vulnerability where SSLv2 is
enabled by a server, even if a client connection is not using
SSLv2. The SSLv2 protocol is widely considered unacceptably broken
and should not be supported. More information is available at
https://www.openssl.org/news/vulnerabilities.html#2016-0800
PR-URL: #5404
rvagg added a commit that referenced this pull request Mar 4, 2016
Notable changes:
* http_parser: Update to http-parser 1.2 to fix an unintentionally
strict limitation of allowable header characters.
(James M Snell) #5242
* domains:
- Prevent an exit due to an exception being thrown rather than
emitting an 'uncaughtException' event on the `process` object when
no error handler is set on the domain within which an error is
thrown and an 'uncaughtException' event listener is set on
`process`. (Julien Gilli) #3887
- Fix an issue where the process would not abort in the proper
function call if an error is thrown within a domain with no error
handler and `--abort-on-uncaught-exception` is used.
(Julien Gilli) #3887
* openssl: Upgrade from 1.0.1r to 1.0.1s
(Ben Noordhuis) #5508
- Fix a double-free defect in parsing malformed DSA keys that may
potentially be used for DoS or memory corruption attacks. It is
likely to be very difficult to use this defect for a practical
attack and is therefore considered low severity for Node.js users.
More info is available at
https://www.openssl.org/news/vulnerabilities.html#2016-0705
- Fix a defect that can cause memory corruption in certain very rare
cases relating to the internal `BN_hex2bn()` and `BN_dec2bn()`
functions. It is believed that Node.js is not invoking the code
paths that use these functions so practical attacks via Node.js
using this defect are _unlikely_ to be possible. More info is
available at
https://www.openssl.org/news/vulnerabilities.html#2016-0797
- Fix a defect that makes the CacheBleed Attack
(https://ssrg.nicta.com.au/projects/TS/cachebleed/) possible.
This defect enables attackers to execute side-channel attacks
leading to the potential recovery of entire RSA private keys. It
only affects the Intel Sandy Bridge (and possibly older)
microarchitecture when using hyper-threading. Newer
microarchitectures, including Haswell, are unaffected. More info
is available at
https://www.openssl.org/news/vulnerabilities.html#2016-0702
- Remove SSLv2 support, the `--enable-ssl2` command line argument
will now produce an error. The DROWN Attack
(https://drownattack.com/) creates a vulnerability where SSLv2 is
enabled by a server, even if a client connection is not using
SSLv2. The SSLv2 protocol is widely considered unacceptably broken
and should not be supported. More information is available at
https://www.openssl.org/news/vulnerabilities.html#2016-0800
PR-URL: #5404
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cryptoIssues and PRs related to the crypto subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@bnoordhuis@indutny@shigeki