The Utf8DecoderBase::WriteUtf16Slow function in unicode-decoder.cc in Google V8, as used in Node.js before 0.12.6, io.js before 1.8.3 and 2.
The Utf8DecoderBase::WriteUtf16Slow function in unicode-decoder.cc in Google V8, as used in Node.js before 0.12.6, io.js before 1.8.3 and 2.x before 2.3.3, and other products, does not verify that there is memory available for a UTF-16 surrogate pair, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted byte sequence.
- Published
- Jul 9, 2015
- Updated
- Jun 16, 2026
- EPSS
- 3.0% · 87th percentile
- CWE
- CWE-119
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.0%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| v8 | cpe:2.3:a:google:v8 | |
| iojs | io.js | cpe:2.3:a:iojs:io.js |
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.jsup to 0.12.5 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-atk | before 2.26.1-2.8.4 | 2.26.1-2.8.4 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-cairo | before 1.15.10-2.13.4 | 1.15.10-2.13.4 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-gdk-pixbuf | before 2.36.11-2.8.4 | 2.36.11-2.8.4 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-glib2 | before 2.54.3-2.14.7 | 2.54.3-2.14.7 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-gtk3 | before 3.10.9-2.15.3 | 3.10.9-2.15.3 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-harfbuzz | before 1.7.5-2.7.4 | 1.7.5-2.7.4 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-libffi | before 3.2.1.git259-2.3.3 | 3.2.1.git259-2.3.3 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-libffi-gcc5 | before 5.3.1+r233831-14.1 | 5.3.1+r233831-14.1 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-pango | before 1.40.14-2.7.4 | 1.40.14-2.7.4 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | mozilla-nspr | before 4.21-29.6.1 | 4.21-29.6.1 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | mozilla-nss | before 3.45-38.9.3 | 3.45-38.9.3 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | MozillaFirefox | before 68.2.0-78.51.4 | 68.2.0-78.51.4 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | MozillaFirefox-branding-SLED | before 68-21.9.8 | 68-21.9.8 |
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-8548Multiple unspecified vulnerabilities in Google V8 before 4.7.80.23, as used in Google Chrome before 47.0.2526.80, allow attackers to cause a40Plan
- CVE-2009-2555Heap-based buffer overflow in src/jsregexp.cc in Google V8 before 1.1.10.14, as used in Google Chrome before 2.0.172.37, allows remote attac38Monitor
- CVE-2016-1678objects.cc in Google V8 before 5.0.71.32, as used in Google Chrome before 51.0.2704.63, does not properly restrict lazy deoptimization, whic35Monitor
- CVE-2016-3679Multiple unspecified vulnerabilities in Google V8 before 4.9.385.33, as used in Google Chrome before 49.0.2623.108, allow attackers to cause35Monitor
- CVE-2015-1242The ReduceTransitionElementsKind function in hydrogen-check-elimination.cc in Google V8 before 4.2.77.8, as used in Google Chrome before 42.31Monitor
- CVE-2014-3152Integer underflow in the LCodeGen::PrepareKeyedOperand function in arm/lithium-codegen-arm.cc in Google V8 before 3.25.28.16, as used in Goo31Monitor
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 |
|---|---|---|
| suse:firefox-atk | 2.26.1-2.8.4 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-cairo | 1.15.10-2.13.4 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-gdk-pixbuf | 2.36.11-2.8.4 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-glib2 | 2.54.3-2.14.7 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-gtk3 | 3.10.9-2.15.3 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-harfbuzz | 1.7.5-2.7.4 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-libffi | 3.2.1.git259-2.3.3 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-libffi-gcc5 | 5.3.1+r233831-14.1 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-pango | 1.40.14-2.7.4 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:mozilla-nspr | 4.21-29.6.1 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:MozillaFirefox | 68.2.0-78.51.4 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:MozillaFirefox-branding-SLED | 68-21.9.8 · SUSE:Linux Enterprise Server 11 SP4-LTSS | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- blog.nodejs.org/2015/07/03/node-v0-12-6-stable/
- www.securityfocus.com/bid/75556
- codereview.chromium.org/1226493003
- github.com/joyent/node/issues/25583
- medium.com/%40iojs/important-security-upgrades-for-node-js-and-io-js-8ac14ece5852
Vendor advisories and official records. Exploit/PoC links are deliberately left out.