dbcve.org
ChromeWeb browser · Google

CVE-2015-6771

HIGH · 7.5 CVSS v2.0 Published 2015-12-06
Fix available
A fix is available. Upgrade to after 46.0.2490.86 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
js/array.js in Google V8, as used in Google Chrome before 47.0.2526.73, improperly implements certain map and filter operations for arrays, 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 confidence

A memory safety vulnerability exists in Google V8's array.js implementation where the map and filter operations fail to properly validate array bounds, allowing out-of-bounds memory access when processing specially crafted JavaScript arrays. This can lead to denial of service or potentially arbitrary code execution.

MitigationUpdate Google Chrome to version 47.0.2526.73 or later. Organizations using V8 in other products (such as Node.js) should update to V8 versions that include the patch for this issue.

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
Affected:<= 46.0.2490.86

CVSS 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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Google Chrome version
    Open Chrome and navigate to chrome://settings/help, or click Help > About Google Chrome
    Affected if The displayed version number is 46.0.2490.86 or lower (for example, 46.0.2490.80, 45.x.x.x, etc.)
  2. Confirm Chrome version is within affected range
    Compare your version number to the affected range: any version <= 46.0.2490.86
    Affected if Your version is 46.0.2490.86 or any earlier version such as 45.x.x.x or 44.x.x.x
  3. Verify JavaScript execution is enabled
    The vulnerability is triggered through JavaScript array operations (map/filter). Ensure Chrome has JavaScript enabled for testing purposes
    Affected if JavaScript is enabled in Chrome settings (this is the default and required for the vulnerability to be exploitable)

You are affected if you are running Google Chrome version 46.0.2490.86 or any earlier version, and JavaScript is enabled in your browser settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 46.0.2490.86
Interim mitigation

Update Google Chrome to version 47.0.2526.73 or later. Organizations using V8 in other products (such as Node.js) should update to V8 versions that include the patch for this issue.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6771 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-6771 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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