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'`…
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 7.7% (FIRST EPSS); higher than 94.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: nodejs (Alpine:v3.10) 8.11.4-r0; nodejs (Debian:12) 10.15.0~dfsg-6; npm (Red Hat:openshift_application_runtimes:1.0::el7) 1:6.2.0-1.10.9.0.1.el7, 1:5.6.0-1.8.11.4.2.el7.
Low priority for now. Upgrade to nodejs (Alpine:v3.10) 8.11.4-r0; nodejs (Debian:12) 10.15.0~dfsg-6; npm (Red Hat:openshift_application_runtimes:1.0::el7) 1:6.2.0-1.10.9.0.1.el7, 1:5.6.0-1.8.11.4.2.el7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 21, 2018
- Updated
- Oct 15, 2026
- EPSS
- 7.7% · 94th percentile
- CWE
- CWE-787
Report tools
Action score
32
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 7.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
| redhat | openshift container platform | cpe:2.3:a:redhat:openshift_container_platform |
Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (nodejs). Independent of NVD's CPE analysis and usually ahead of it.
The Node.js Project Node.js
- All versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.jsbefore 6.14.4
- nodejs node.js8.0.0 and later · before 8.11.4
- nodejs node.js10.0.0 and later · before 10.9.0
- redhat openshift container platform3.11
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | nodejs | before 8.11.4-r0 | 8.11.4-r0 |
| Debian:12 | nodejs | before 10.15.0~dfsg-6 | 10.15.0~dfsg-6 |
| Red Hat:openshift_application_runtimes:1.0::el7 | npm | before 1:6.2.0-1.10.9.0.1.el7 | 1:6.2.0-1.10.9.0.1.el7 |
| Red Hat:openshift_application_runtimes:1.0::el7 | npm | before 1:5.6.0-1.8.11.4.2.el7 | 1:5.6.0-1.8.11.4.2.el7 |
| Red Hat:openshift_application_runtimes:1.0::el7 | rhoar-nodejs | before 1:10.9.0-1.el7 | 1:10.9.0-1.el7 |
| Red Hat:openshift_application_runtimes:1.0::el7 | rhoar-nodejs | before 1:8.11.4-2.el7 | 1:8.11.4-2.el7 |
| Red Hat:openshift_application_runtimes:1.0::el7 | rhoar-nodejs-debuginfo | before 1:8.11.4-2.el7 | 1:8.11.4-2.el7 |
| Red Hat:openshift_application_runtimes:1.0::el7 | rhoar-nodejs-debuginfo | before 1:10.9.0-1.el7 | 1:10.9.0-1.el7 |
| Red Hat:openshift_application_runtimes:1.0::el7 | rhoar-nodejs-docs | before 1:10.9.0-1.el7 | 1:10.9.0-1.el7 |
| Red Hat:openshift_application_runtimes:1.0::el7 | rhoar-nodejs-docs | before 1:8.11.4-2.el7 | 1:8.11.4-2.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients-redistributable | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-docker-excluder | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-excluder | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hyperkube | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hypershift | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-master | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-node | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-pod | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-sdn-ovs | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-template-service-broker | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-tests | before 0:3.11.43-1.git.0.647ac05.el7 | 0:3.11.43-1.git.0.647ac05.el7 |
| Red Hat:openshift:3.11::el7 | jenkins-2-plugins | before 0:3.11.1539805268-1.el7 | 0:3.11.1539805268-1.el7 |
| Red Hat:openshift:3.11::el7 | kibana | before 0:5.6.12-1.el7 | 0:5.6.12-1.el7 |
+16
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed56Plan
- CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an…53Plan
- CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory…50Plan
Published before and after this one in the same product
- ← EarlierCVE-2018-7164Jun 13, 2018 · Node.js versions 9.7.0 and later and 10.x are vulnerable and the severity is MEDIUM.32Monitor
- ← EarlierCVE-2018-7167Jun 13, 2018 · Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Denial of Service.32Monitor
- Later →CVE-2018-7166Aug 21, 2018 · In all versions of Node.js 10 prior to 10.9.0, an argument processing flaw can cause `Buffer.alloc()` to return uninitialized memory.31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:nodejs | 8.11.4-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:nodejs | 10.15.0~dfsg-6 · Debian:12 | Package registry (OSV) |
| red hat:npm | 1:5.6.0-1.8.11.4.2.el7 · Red Hat:openshift_application_runtimes:1.0::el7 | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs | 0:6.11.3-6.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs-debuginfo | 0:6.11.3-6.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs-devel | 0:6.11.3-6.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs-docs | 0:6.11.3-6.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs | 0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs-debuginfo | 0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs-devel | 0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs-docs | 0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rhoar-nodejs | 1:8.11.4-2.el7 · Red Hat:openshift_application_runtimes:1.0::el7 | Package registry (OSV) |
| red hat:rhoar-nodejs-debuginfo | 1:8.11.4-2.el7 · Red Hat:openshift_application_runtimes:1.0::el7 | Package registry (OSV) |
| red hat:rhoar-nodejs-docs | 1:8.11.4-2.el7 · Red Hat:openshift_application_runtimes:1.0::el7 | Package registry (OSV) |
| suse:nodejs4 | 4.9.1-15.14.1 · SUSE:Linux Enterprise Module for Web and Scripting 12 | Package registry (OSV) |
| suse:nodejs6 | 6.14.4-11.18.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:nodejs8 | 8.11.4-3.8.2 · SUSE:Linux Enterprise Module for Web and Scripting 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.