CVE-2018-12115: High severity F5 BIG-IP vulnerability

Published Aug 12, 2018
·
Updated

CVE-2018-7167 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-12115 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-12116 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.

Other sources

Node.js TSC member Сковорода Никита Андреевич (Nikita Skovoroda / @ChALkeR) 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.

Impact:

All previous versions of Node.js 6.x (LTS "Boron") are vulnerable All previous versions of Node.js 8.x (LTS "Carbon") are vulnerable All previous versions of Node.js 10.x (Current) are vulnerable

References:

https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/

Red Hat

Affected Software

13 affected componentsFixes available
redhat/nodejs<10.9.0
10.9.0
redhat/nodejs<8.11.4
8.11.4
redhat/nodejs<6.14.4
6.14.4
Nodejs Node.js<6.14.4
Nodejs Node.js>=8.0.0<8.11.4
Nodejs Node.js>=10.0.0<10.9.0
redhat OpenShift Container Platform=3.11
F5 BIG-IP>=17.1.0<=17.1.2
17.5.017.1.2.2
F5 BIG-IP>=16.1.0<=16.1.5
16.1.6
F5 BIG-IP>=15.1.0<=15.1.10
F5 BIG-IP>=14.1.0<=14.1.5
F5 BIG-IP>=13.1.0<=13.1.5
F5 BIG-IQ Centralized Management>=8.0.0<=8.4.0
8.4.1

Event History

Aug 21, 2018
CVE Published
12:29 PM
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionWeakness
Oct 2, 2023
Advisory Published
via F5·08:54 PM
Data Sourced
via F5·08:54 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2018-12115?

CVE-2018-12115 has been classified as a Denial of Service vulnerability.

2

How do I fix CVE-2018-12115?

To mitigate CVE-2018-12115, update Node.js to versions 6.14.4, 8.11.4, or 10.9.0.

3

What software is affected by CVE-2018-12115?

CVE-2018-12115 affects specific versions of Node.js and F5 BIG-IP products.

4

Can CVE-2018-12115 be exploited remotely?

Yes, CVE-2018-12115 can be exploited remotely, potentially leading to denial of service.

5

What are the symptoms of an exploit of CVE-2018-12115?

The primary symptom of an exploit of CVE-2018-12115 is a hang in the application, resulting in a denial of service.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203