-
Notifications
You must be signed in to change notification settings - Fork 30k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
tls: emit
session
after verifying certificate
Prior to this patch `session` event was emitted after `secure` event on TLSSocket, but before `secureConnect` event. This is problematic for `https.Agent` because it must cache session only after verifying the remote peer's certificate. Connecting to a server that presents an invalid certificate resulted in the session being cached after the handshake with the server and evicted right after a certifiate validation error and socket's destruction. A request initiated during this narrow window would pick the faulty session, send it to the malicious server and skip the verification of the server's certificate. Fixes: https://hackerone.com/reports/811502 CVE-ID: CVE-2020-8172 PR-URL: nodejs-private/node-private#200 Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
- Loading branch information
Showing
3 changed files
with
122 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
'use strict'; | ||
const common = require('../common'); | ||
const assert = require('assert'); | ||
|
||
if (!common.hasCrypto) | ||
common.skip('missing crypto'); | ||
|
||
const https = require('https'); | ||
const fixtures = require('../common/fixtures'); | ||
|
||
const options = { | ||
key: fixtures.readKey('agent1-key.pem'), | ||
|
||
// NOTE: Certificate Common Name is 'agent1' | ||
cert: fixtures.readKey('agent1-cert.pem'), | ||
|
||
// NOTE: TLS 1.3 creates new session ticket **after** handshake so | ||
// `getSession()` output will be different even if the session was reused | ||
// during the handshake. | ||
secureProtocol: 'TLSv1_2_method' | ||
}; | ||
|
||
const ca = [ fixtures.readKey('ca1-cert.pem') ]; | ||
|
||
const server = https.createServer(options, function(req, res) { | ||
res.end('ok'); | ||
}).listen(0, common.mustCall(function() { | ||
const port = this.address().port; | ||
|
||
const req = https.get({ | ||
port, | ||
path: '/', | ||
ca, | ||
servername: 'nodejs.org', | ||
}, common.mustNotCall(() => {})); | ||
|
||
req.on('error', common.mustCall((err) => { | ||
assert.strictEqual( | ||
err.message, | ||
'Hostname/IP does not match certificate\'s altnames: ' + | ||
'Host: nodejs.org. is not cert\'s CN: agent1'); | ||
|
||
const second = https.get({ | ||
port, | ||
path: '/', | ||
ca, | ||
servername: 'nodejs.org', | ||
}, common.mustNotCall(() => {})); | ||
|
||
second.on('error', common.mustCall((err) => { | ||
server.close(); | ||
|
||
assert.strictEqual( | ||
err.message, | ||
'Hostname/IP does not match certificate\'s altnames: ' + | ||
'Host: nodejs.org. is not cert\'s CN: agent1'); | ||
})); | ||
})); | ||
})); |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
'use strict'; | ||
const common = require('../common'); | ||
if (!common.hasCrypto) | ||
common.skip('missing crypto'); | ||
const fixtures = require('../common/fixtures'); | ||
const assert = require('assert'); | ||
const tls = require('tls'); | ||
|
||
const options = { | ||
key: fixtures.readKey('agent1-key.pem'), | ||
|
||
// NOTE: Certificate Common Name is 'agent1' | ||
cert: fixtures.readKey('agent1-cert.pem'), | ||
|
||
// NOTE: TLS 1.3 creates new session ticket **after** handshake so | ||
// `getSession()` output will be different even if the session was reused | ||
// during the handshake. | ||
secureProtocol: 'TLSv1_2_method' | ||
}; | ||
|
||
const server = tls.createServer(options, common.mustCall((socket) => { | ||
socket.end(); | ||
})).listen(0, common.mustCall(() => { | ||
let connected = false; | ||
let session = null; | ||
|
||
const client = tls.connect({ | ||
rejectUnauthorized: false, | ||
port: server.address().port, | ||
}, common.mustCall(() => { | ||
assert(!connected); | ||
assert(!session); | ||
|
||
connected = true; | ||
})); | ||
|
||
client.on('session', common.mustCall((newSession) => { | ||
assert(connected); | ||
assert(!session); | ||
|
||
session = newSession; | ||
|
||
client.end(); | ||
server.close(); | ||
})); | ||
})); |