FedoraOperating system · Fedoraproject
CVE-2014-3152
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 · uneditedInteger underflow in the LCodeGen::PrepareKeyedOperand function in arm/lithium-codegen-arm.cc in Google V8 before 3.25.28.16, as used in Google Chrome before 35.0.1916.114, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger a negative key value.
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 confidenceInteger underflow vulnerability in Google V8's ARM lithium code generator (LCodeGen::PrepareKeyedOperand function) allows negative key values to trigger the underflow, potentially causing memory corruption leading to denial of service or unspecified impact.
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
FedoraOperating system
= 20= 21= 22
ChromeWeb browser
<= 35.0.1916.113= 35.0.1916.0= 35.0.1916.1= 35.0.1916.2= 35.0.1916.3= 35.0.1916.4= 35.0.1916.5= 35.0.1916.6= 35.0.1916.7= 35.0.1916.8= 35.0.1916.9= 35.0.1916.10<= 3.25.28= 3.25.0= 3.25.1= 3.25.2= 3.25.3= 3.25.4= 3.25.5= 3.25.6= 3.25.7= 3.25.8= 3.25.9= 3.25.10CVSS 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.
-
Check Google Chrome versionOpen chrome://version in the browser or run 'google-chrome --version' from command lineAffected if Version is 35.0.1916.113 or lower, or matches any of the affected 35.0.1916.x versions listed (0 through 13)
-
Check V8 JavaScript engine version embedded in ChromeOpen chrome://version and look for the V8 version string, or enter 'navigator.userAgent' in developer console to see version infoAffected if V8 version is 3.25.28 or lower, or matches any of the affected 3.25.x versions listed (0 through 10)
-
Check system architectureRun 'uname -m' or 'arch' from command line to identify processor architectureAffected if System is running on ARM architecture (arm, armv7l, aarch64) - this vulnerability specifically affects the ARM lithium code generator
-
Confirm Chrome is using the V8 engineOpen chrome://components and verify V8 is listed, or run JavaScript in console and check that it executesAffected if V8 engine is present and enabled - the vulnerability exists in the V8 component itself
You are affected if running Google Chrome 35.0.1916.113 or earlier with V8 3.25.28 or earlier on an ARM-based system, or any of the specific version numbers listed in the affected ranges.
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 35.0.1916.114 or later and ensure V8 engine is updated to version 3.25.28.16 or later to address this vulnerability.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3152 — 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-3152 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