First published: Thu Jul 09 2015(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Google V8 | ||
Io.js | <=1.8.2 | |
Io.js | =2.0.0 | |
Io.js | =2.0.1 | |
Io.js | =2.0.2 | |
Io.js | =2.1.0 | |
Io.js | =2.2.0 | |
Io.js | =2.2.1 | |
Io.js | =2.3.0 | |
Io.js | =2.3.1 | |
Io.js | =2.3.2 | |
Node.js | <=0.12.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-5380 is considered a high severity vulnerability due to its potential to cause denial of service.
To fix CVE-2015-5380, upgrade your Node.js to version 0.12.6 or later, or io.js to version 1.8.3 or later.
CVE-2015-5380 affects Node.js versions before 0.12.6 and io.js versions before 1.8.3.
The impact of CVE-2015-5380 is the ability for remote attackers to cause a denial of service through crafted UTF-16 surrogate pairs.
Yes, CVE-2015-5380 originates from a vulnerability in the Utf8DecoderBase::WriteUtf16Slow function used in Google V8.