Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1379921 - (CVE-2016-7099) CVE-2016-7099 nodejs: wildcard certificates not properly validated
CVE-2016-7099 nodejs: wildcard certificates not properly validated
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
impact=important,public=20160928,repo...
: Security
Depends On: 1379922 1392912 1392913 1392914 1392915 1399557 1417856 1417957 1417958 1470252 1470253 1470254 1470255
Blocks: 1346916 1394602
  Show dependency tree / graph
 
Reported: 2016-09-28 02:35 EDT by Martin Prpič
Modified: 2018-07-30 06:28 EDT (History)
47 users (show)

See Also:
Fixed In Version: nodejs 6.7.0, nodejs 4.6.0, nodejs 0.12.16, nodejs 0.10.47
Doc Type: If docs needed, set a value
Doc Text:
It was found that Node.js' tls.checkServerIdentity() function did not properly validate server certificates containing wildcards. A malicious TLS server could use this flaw to get a specially crafted certificate accepted by a Node.js TLS client.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:0002 normal SHIPPED_LIVE Important: rh-nodejs4-nodejs and rh-nodejs4-http-parser security update 2017-01-02 15:55:58 EST

  None (edit)
Description Martin Prpič 2016-09-28 02:35:23 EDT 
The following flaw was reported in Node.js:

This is a high severity defect that would allow a malicious TLS server to serve an invalid wildcard certificate for its hostname and be improperly validated by a Node.js client. This is due to a flaw in the validation of *. in the wildcard name string.

External References:

https://nodejs.org/en/blog/vulnerability/september-2016-security-releases/
Comment 1 Martin Prpič 2016-09-28 02:36:46 EDT 
Created nodejs tracking bugs for this issue:

Affects: fedora-all [bug 1379922]
Comment 6 Cedric Buissart 2016-11-08 09:29:03 EST 
Marking nodejs010-nodejs as WONTFIX because nodejs010 is past EOL.
For further information regarding Software Collection package life cycle policy, see :
https://access.redhat.com/support/policy/updates/rhscl/
Comment 9 errata-xmlrpc 2017-01-02 10:56:52 EST 
This issue has been addressed in the following products:

  Red Hat Software Collections for Red Hat Enterprise Linux 6
  Red Hat Software Collections for Red Hat Enterprise Linux 6.7 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 7
  Red Hat Software Collections for Red Hat Enterprise Linux 7.2 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 7.3 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 7.1 EUS

Via RHSA-2017:0002 https://rhn.redhat.com/errata/RHSA-2017-0002.html
Comment 13 Jason Shepherd 2018-04-02 23:49:47 EDT 
Openshift Enterprise points to rhscl/nodejs-4-rhel7 image which includes node 4.6.2, see:
https://github.com/openshift/library/blob/master/official/nodejs/imagestreams/nodejs-rhel7.json

Marking Openshift Enterprise as notaffected.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.