ChromeWeb browser · Google
CVE-2015-6764
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe BasicJsonStringifier::SerializeJSArray function in json-stringifier.h in the JSON stringifier in Google V8, as used in Google Chrome before 47.0.2526.73, improperly loads array elements, which allows remote attackers to cause a denial of service (out-of-bounds memory access) or possibly have unspecified other impact via crafted JavaScript code.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceV8 JavaScript engine vulnerability in the JSON stringifier's SerializeJSArray function (json-stringifier.h) allows out-of-bounds memory access when processing crafted JavaScript arrays. This can cause denial of service or potentially enable arbitrary code execution via malicious JavaScript code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
<= 46.0.2490.86
Node.jsApplication
>= 4.0.0, <= 4.1.2>= 4.2.0, < 4.2.3>= 5.0.0, <= 5.1.1
Debian LinuxOperating system
= 8.0= 9.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionOpen Chrome and navigate to chrome://version, or go to Settings > About Chrome to view the version numberAffected if Version is 46.0.2490.86 or lower
-
Check Node.js versionRun 'node --version' in a terminal to display the installed Node.js versionAffected if Version is 4.0.0 through 4.1.2, 4.2.0 through 4.2.2, or 5.0.0 through 5.1.1
-
Verify V8 JSON stringifier is accessibleExecute 'node -e "console.log(JSON.stringify({test:'value'}))"' to confirm JSON functionality is workingAffected if JSON.stringify executes successfully, meaning the vulnerable V8 JSON stringifier code path is present
You are affected if you are running Chrome 46.0.2490.86 or lower, or any Node.js version 4.0.0-4.1.2, 4.2.0-4.2.2, or 5.0.0-5.1.1, and your application uses the JSON.stringify function which invokes the vulnerable SerializeJSArray code in V8.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.2.3
Update Google Chrome to version 47.0.2526.73 or later to patch the vulnerable V8 engine. For embedded V8 implementations, rebuild with the patched V8 version.
Chrome: 47.0.2526.73+ | Node.js: 4.2.3+ or 5.1.2+ or later LTS branches
- For Chrome/Chromium: Update browser to version 47.0.2526.73 or later
- For Node.js: Upgrade to a fixed version - Node.js 4.2.3+, 4.1.3+, or 5.1.2+ (or to a later stable branch such as Node.js 4.x LTS or 6.x+)
- For Debian: Apply security updates from Debian security repositories for the V8 library package (CVE-2015-6764)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6764 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-6764 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data