ChromeWeb browser · Google
CVE-2014-7927
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 SimplifiedLowering::DoLoadBuffer function in compiler/simplified-lowering.cc in Google V8, as used in Google Chrome before 40.0.2214.91, does not properly choose an integer data type, which allows remote attackers to cause a denial of service (memory corruption) 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 confidenceThis is a type selection bug in the V8 JavaScript engine's compiler optimization pass. The SimplifiedLowering::DoLoadBuffer function incorrectly chooses an integer data type during compilation, leading to memory corruption when processing crafted JavaScript code. The vulnerability allows remote code execution or denial of service via malicious JavaScript.
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
<= 40.0.2214.85CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installedCheck for Chrome installation: On Windows, look in C:\Program Files\Google\Chrome\Application\ or C:\Program Files (x86)\Google\Chrome\Application\. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or /opt/google/chrome/google-chrome.Affected if Google Chrome is found on the system
-
Retrieve the installed Chrome version numberRun 'google-chrome --version' on Linux/Mac, or right-click chrome.exe and select Properties > Details > File Version on Windows. Alternatively, navigate to chrome://settings/help in the browser to view the version.Affected if Unable to determine the version number
-
Compare version against vulnerable rangeCompare the installed version to the affected range: any version less than or equal to 40.0.2214.85 is vulnerable. Note that version 40.0.2214.85 itself is also affected; only versions 40.0.2214.91 and later are patched.Affected if Installed version is 40.0.2214.85 or earlier
A user is affected if Google Chrome version 40.0.2214.85 or earlier is installed on their system.
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.
From vendor dataUpdate Google Chrome to version 40.0.2214.91 or later. For other products using the V8 engine, apply the corresponding patch to compiler/simplified-lowering.cc that corrects the integer data type selection logic in SimplifiedLowering::DoLoadBuffer.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7927 — 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-2014-7927 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