In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding (recognized by Node.js under the names `'ucs2'`, `'ucs-2'`, `'utf16le'` and `'utf-16le'`), `Buffer#write()` can be abused to write outside of the bounds of a single `Buffer`. Writes that start from the second-to-last position of a buffer cause a miscalculation of the maximum length of the input bytes to be written.

The remote Ubuntu 16.04 ESM / 18.04 ESM host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-4796-1 advisory.

  - The tls.checkServerIdentity function in Node.js 0.10.x before 0.10.47, 0.12.x before 0.12.16, 4.x before     4.6.0, and 6.x before 6.7.0 does not properly handle wildcards in name fields of X.509 certificates, which     allows man-in-the-middle attackers to spoof servers via a crafted certificate. (CVE-2016-7099)

  - The c-ares function `ares_parse_naptr_reply()`, which is used for parsing NAPTR responses, could be     triggered to read memory outside of the given input buffer if the passed in DNS response packet was     crafted in a particular way. (CVE-2017-1000381)

  - In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding (recognized by     Node.js under the names `'ucs2'`, `'ucs-2'`, `'utf16le'` and `'utf-16le'`), `Buffer#write()` can be abused     to write outside of the bounds of a single `Buffer`. Writes that start from the second-to-last position of     a buffer cause a miscalculation of the maximum length of the input bytes to be written. (CVE-2018-12115)

  - Node.js: All versions prior to Node.js 6.15.0 and 8.14.0: HTTP request splitting: If Node.js can be     convinced to use unsanitized user-provided Unicode data for the `path` option of an HTTP request, then     data can be provided which will trigger a second, unexpected, and user-defined HTTP request to made to the     same server. (CVE-2018-12116)

  - Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Slowloris HTTP Denial of     Service: An attacker can cause a Denial of Service (DoS) by sending headers very slowly keeping HTTP or     HTTPS connections and associated resources alive for a long period of time. (CVE-2018-12122)

  - Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Hostname spoofing in URL parser     for javascript protocol: If a Node.js application is using url.parse() to determine the URL hostname, that     hostname can be spoofed by using a mixed case javascript: (e.g. javAscript:) protocol (other protocols     are not affected). If security decisions are made about the URL based on the hostname, they may be     incorrect. (CVE-2018-12123)

  - The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited     to perform remote code execution. An attack is possible from malicious websites open in a web browser on     the same computer, or another computer with network access to the computer running the Node.js process. A     malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy     checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process     with the debug port active is running on localhost or on a host on the local network, the malicious     website could connect to it as a debugger, and get full code execution access. (CVE-2018-7160)

  - Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a     Denial of Service. In order to address this vulnerability, the implementations of Buffer.alloc() and     Buffer.fill() were updated so that they zero fill instead of hanging in these cases. All versions of     Node.js 6.x (LTS Boron), 8.x (LTS Carbon), and 9.x are vulnerable. All versions of Node.js 10.x     (Current) are NOT vulnerable. (CVE-2018-7167)

  - In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1,     an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive     mode and by sending headers very slowly. This keeps the connection and associated resources alive for a     long period of time. Potential attacks are mitigated by the use of a load balancer or other proxy layer.
    This vulnerability is an extension of CVE-2018-12121, addressed in November and impacts all active Node.js     release lines including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before     11.10.1. (CVE-2019-5737)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of F5 Networks BIG-IP installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the K000137093 advisory.

  - Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a     Denial of Service. In order to address this vulnerability, the implementations of Buffer.alloc() and     Buffer.fill() were updated so that they zero fill instead of hanging in these cases. All versions of     Node.js 6.x (LTS Boron), 8.x (LTS Carbon), and 9.x are vulnerable. All versions of Node.js 10.x     (Current) are NOT vulnerable. (CVE-2018-7167)

  - In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding (recognized by     Node.js under the names `'ucs2'`, `'ucs-2'`, `'utf16le'` and `'utf-16le'`), `Buffer#write()` can be abused     to write outside of the bounds of a single `Buffer`. Writes that start from the second-to-last position of     a buffer cause a miscalculation of the maximum length of the input bytes to be written. (CVE-2018-12115)

  - Node.js: All versions prior to Node.js 6.15.0 and 8.14.0: HTTP request splitting: If Node.js can be     convinced to use unsanitized user-provided Unicode data for the `path` option of an HTTP request, then     data can be provided which will trigger a second, unexpected, and user-defined HTTP request to made to the     same server. (CVE-2018-12116)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote host is affected by the vulnerability described in GLSA-202003-48 (Node.js: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Node.js. Please review       the CVE identifiers referenced below for details.
  Impact :

    A remote attacker could possibly write arbitrary files, cause a Denial       of Service condition or can conduct HTTP request splitting attacks.
  Workaround :

    There is no known workaround at this time.

This update for nodejs8 to version 8.11.4 fixes the following issues :

Security issues fixed :

  - CVE-2018-12115: Fixed an out-of-bounds memory write in     Buffer that could be used to write to memory outside of     a Buffer's memory space buffer (bsc#1105019)

  - Upgrade to OpenSSL 1.0.2p, which fixed :

  - CVE-2018-0732: Client denial-of-service due to large DH     parameter (bsc#1097158)

  - ECDSA key extraction via local side-channel

Other changes made :

  - Recommend same major version npm package (bsc#1097748)

  - Fix parallel/test-tls-passphrase.js test to continue to     function with older versions of OpenSSL library.

This update was imported from the SUSE:SLE-15:Update update project.

This update for nodejs8 to version 8.11.4 fixes the following issues :

Security issues fixed :

CVE-2018-12115: Fixed an out-of-bounds memory write in Buffer that could be used to write to memory outside of a Buffer's memory space buffer (bsc#1105019)

Upgrade to OpenSSL 1.0.2p, which fixed :

  - CVE-2018-0732: Client denial-of-service due to large DH     parameter (bsc#1097158)

  - ECDSA key extraction via local side-channel

Other changes made: Recommend same major version npm package (bsc#1097748)

Fix parallel/test-tls-passphrase.js test to continue to function with older versions of OpenSSL library.

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for nodejs6 to version 6.14.4 fixes the following issues :

Security issues fixed :

  - CVE-2018-12115: Fixed an out-of-bounds (OOB) write in     Buffer.write() for UCS-2 encoding (bsc#1105019)     CVE-2018-0732: Upgrade to OpenSSL 1.0.2p, fixing a     client DoS due to large DH parameter (bsc#1097158)

Other issues fixed :

Recommend same major version npm package (bsc#1097748)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for nodejs4 fixes the following issues :

Security issues fixed :

CVE-2018-12115: Fixed an out-of-bounds memory write in Buffer that could be used to write to memory outside of a Buffer's memory space buffer (bsc#1105019)

Upgrade to OpenSSL 1.0.2p, which fixed :

  - CVE-2018-0732: Client denial-of-service due to large DH     parameter (bsc#1097158)

  - ECDSA key extraction via local side-channel

Other changes made: Recommend same major version npm package (bsc#1097748)

Use absolute paths in executable shebang lines

Fix building with ICU61.1 (bsc#1091764)

Install license with %license, not %doc (bsc#1082318)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

An update is now available for Red Hat OpenShift Container Platform 3.11.

Red Hat Product Security has rated this update as having a security impact of Critical. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Red Hat OpenShift Container Platform is Red Hat's cloud computing Kubernetes application platform solution designed for on-premise or private cloud deployments.

Security Fix(es) :

* A privilege escalation vulnerability exists in OpenShift Container Platform 3.x which allows for compromise of pods running on a compute node to which a pod is scheduled with normal user privilege. This access could include access to all secrets, pods, environment variables, running pod/container processes, and persistent volumes, including in privileged containers. Additionally, on versions 3.6 and higher of OpenShift Container Platform, this vulnerability allows cluster-admin level access to any API hosted by an aggregated API server. This includes the 'servicecatalog' API which is installed by default in 3.7 and later. Cluster-admin level access to the service catalog allows creation of brokered services by an unauthenticated user with escalated privileges in any namespace and on any node. This could lead to an attacker being allowed to deploy malicious code, or alter existing services. (CVE-2018-1002105)

* nodejs: Out of bounds (OOB) write via UCS-2 encoding (CVE-2018-12115)

* kibana: Cross-site scripting via the source field formatter (CVE-2018-3830)

Space precludes documenting all of the bug fixes and enhancements in this advisory. See the following Release Notes documentation for details about these changes :

https://docs.openshift.com/container-platform/3.11/release_notes/ ocp_3_11_release_notes.html

All OpenShift Container Platform 3.11 users are advised to upgrade to these updated packages and images.

An update is now available for Red Hat OpenShift Application Runtimes.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Red Hat Openshift Application Runtimes provides an application platform that reduces the complexity of developing and operating applications (monoliths and microservices) for OpenShift as a containerized platform.

This release of RHOAR Node.js 10.9.0 serves as a replacement for RHOAR Node.js 10.8.0, and includes bug fixes and enhancements. For further information, refer to the Release Notes linked to in the References section.

Security Fix(es) :

* openssl: Malicious server can send large prime to client during DH(E) TLS handshake causing the client to hang (CVE-2018-0732)

* nodejs: Unintentional exposure of uninitialized memory (CVE-2018-7166)

* nodejs: Out of bounds (OOB) write via UCS-2 encoding (CVE-2018-12115)

For more details about the security issue(s), including the impact, a CVSS score, and other related information, refer to the CVE page(s) listed in the References section.

An update is now available for Red Hat OpenShift Application Runtimes.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Red Hat Openshift Application Runtimes provides an application platform that reduces the complexity of developing and operating applications (monoliths and microservices) for OpenShift as a containerized platform.

This release of RHOAR Node.js 8.11.4 serves as a replacement for RHOAR Node.js 8.11.3, and includes bug fixes and enhancements. For further information, refer to the Release Notes linked to in the References section.

Security Fix(es) :

* openssl: Malicious server can send large prime to client during DH(E) TLS handshake causing the client to hang (CVE-2018-0732)

* nodejs: Out of bounds (OOB) write via UCS-2 encoding (CVE-2018-12115)

For more details about the security issue(s), including the impact, a CVSS score, and other related information, refer to the CVE page(s) listed in the References section.

The version of Node.js installed on the remote host is 6.x prior to 6.14.4, 8.x prior to 8.11.4 or 10.x prior to 10.9.0. It is, therefore, affected by multiple vulnerabilities.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

This update for nodejs6 to version 6.14.4 fixes the following issues :

Security issues fixed :

CVE-2018-12115: Fixed an out-of-bounds (OOB) write in Buffer.write() for UCS-2 encoding (bsc#1105019) CVE-2018-0732: Upgrade to OpenSSL 1.0.2p, fixing a client DoS due to large DH parameter (bsc#1097158)

Other issues fixed :

  - Recommend same major version npm package (bsc#1097748)

This update was imported from the SUSE:SLE-12:Update update project.

This update for nodejs4 fixes the following issues :

Security issues fixed :

  - CVE-2018-12115: Fixed an out-of-bounds memory write in     Buffer that could be used to write to memory outside of     a Buffer's memory space buffer (bsc#1105019)

  - Upgrade to OpenSSL 1.0.2p, which fixed :

  - CVE-2018-0732: Client denial-of-service due to large DH     parameter (bsc#1097158)

  - ECDSA key extraction via local side-channel

Other changes made :

  - Recommend same major version npm package (bsc#1097748)

  - Use absolute paths in executable shebang lines

  - Fix building with ICU61.1 (bsc#1091764)

  - Install license with %license, not %doc (bsc#1082318)

This update was imported from the SUSE:SLE-12:Update update project.

Node.js reports : OpenSSL: Client DoS due to large DH parameter This fixes a potential denial of service (DoS) attack against client connections by a malicious server. During a TLS communication handshake, where both client and server agree to use a cipher-suite using DH or DHE (Diffie-Hellman, in both ephemeral and non-ephemeral modes), a malicious server can send a very large prime value to the client. Because this has been unbounded in OpenSSL, the client can be forced to spend an unreasonably long period of time to generate a key, potentially causing a denial of service. OpenSSL: ECDSA key extraction via local side-channel Attackers with access to observe cache-timing may be able to extract DSA or ECDSA private keys by causing the victim to create several signatures and watching responses. This flaw does not have a CVE due to OpenSSL policy to not assign itself CVEs for local-only vulnerabilities that are more academic than practical. This vulnerability was discovered by Keegan Ryan at NCC Group and impacts many cryptographic libraries including OpenSSL. Unintentional exposure of uninitialized memory Only Node.js 10 is impacted by this flaw.

Node.js TSC member Nikita Skovoroda discovered an argument processing flaw that causes Buffer.alloc() to return uninitialized memory. This method is intended to be safe and only return initialized, or cleared, memory. The third argument specifying encoding can be passed as a number, this is misinterpreted by Buffer's internal 'fill' method as the start to a fill operation. This flaw may be abused where Buffer.alloc() arguments are derived from user input to return uncleared memory blocks that may contain sensitive information. Out of bounds (OOB) write Node.js TSC member Nikita Skovoroda discovered an OOB write in Buffer that can be used to write to memory outside of a Buffer's memory space. This can corrupt unrelated Buffer objects or cause the Node.js process to crash.

When used with UCS-2 encoding (recognized by Node.js under the names 'ucs2', 'ucs-2', 'utf16le' and 'utf-16le'), Buffer#write() can be abused to write outside of the bounds of a single Buffer. Writes that start from the second-to-last position of a buffer cause a miscalculation of the maximum length of the input bytes to be written.

ID	Name	Product	Family	Severity
183156	Ubuntu 16.04 ESM / 18.04 ESM : Node.js vulnerabilities (USN-4796-1)	Nessus	Ubuntu Local Security Checks	high
182423	F5 Networks BIG-IP : Node.js vulnerabilities (K000137093)	Nessus	F5 Networks Local Security Checks	high
134776	GLSA-202003-48 : Node.js: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	critical
123312	openSUSE Security Update : nodejs8 (openSUSE-2019-718)	Nessus	SuSE Local Security Checks	high
120104	SUSE SLES15 Security Update : nodejs8 (SUSE-SU-2018:2812-1)	Nessus	SuSE Local Security Checks	high
120103	SUSE SLES12 Security Update : nodejs6 (SUSE-SU-2018:2796-1)	Nessus	SuSE Local Security Checks	high
120093	SUSE SLES12 Security Update : nodejs4 (SUSE-SU-2018:2647-1)	Nessus	SuSE Local Security Checks	high
119408	RHEL 7 : OpenShift Container Platform 3.11 (RHSA-2018:3537)	Nessus	Red Hat Local Security Checks	critical
119403	RHEL 7 : Red Hat OpenShift Application Runtimes Node.js 10.9.0 (RHSA-2018:2553)	Nessus	Red Hat Local Security Checks	high
119402	RHEL 7 : Red Hat OpenShift Application Runtimes Node.js 8.11.4 (RHSA-2018:2552)	Nessus	Red Hat Local Security Checks	high
118937	Node.js Multiple Vulnerabilities (August 2018 Security Releases)	Nessus	Misc.	high
117790	openSUSE Security Update : nodejs8 (openSUSE-2018-1047)	Nessus	SuSE Local Security Checks	high
117689	openSUSE Security Update : nodejs6 (openSUSE-2018-1041)	Nessus	SuSE Local Security Checks	high
117381	openSUSE Security Update : nodejs4 (openSUSE-2018-991)	Nessus	SuSE Local Security Checks	high
112128	FreeBSD : node.js -- multiple vulnerabilities (0904e81f-a89d-11e8-afbb-bc5ff4f77b71)	Nessus	FreeBSD Local Security Checks	high

Detections

Analytics

CVE-2018-12115

high

Tenable Plugins

high

high

critical

high

high

high

high

critical

high

high

high

high

high

high

high