ChromeWeb browser · Google
CVE-2015-1290
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 Google V8 engine, as used in Google Chrome before 44.0.2403.89 and QtWebEngineCore in Qt before 5.5.1, allows remote attackers to cause a denial of service (memory corruption) or execute arbitrary code via a crafted web site.
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 confidenceA memory corruption vulnerability exists in the Google V8 JavaScript engine, affecting Google Chrome prior to 44.0.2403.89 and QtWebEngineCore in Qt before 5.5.1. Remote attackers can exploit this via maliciously crafted websites to cause denial of service through memory corruption or achieve arbitrary code execution.
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
< 44.0.2403.89< 5.5.1= 42.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 Help > About Google Chrome. The version number is displayed next to 'Google Chrome'Affected if The displayed version is earlier than 44.0.2403.89
-
Check Chromium-based browser versionFor browsers based on Chromium (not Chrome), check the built-in version information typically found in Help > About or by entering chrome://version in the address barAffected if The Chromium version is earlier than 44.0.2403.89 (the Chromium version that corresponds to Chrome 44.0.2403.89)
-
Identify Qt version installedRun 'qmake -query QT_VERSION' from command line, or inspect the Qt libraries in the installation directory (typically in /usr/lib/qt5 or similar path)Affected if The Qt version shown is earlier than 5.5.1
-
Check for QtWebEngine usageReview application dependencies or search for QtWebEngineCore library files on the system: find /usr -name 'libQt5WebEngineCore*' 2>/dev/nullAffected if QtWebEngineCore is present and the Qt version is earlier than 5.5.1
A system is affected if Google Chrome or any Chromium-based browser version is below 44.0.2403.89, OR if Qt with QtWebEngine version is below 5.5.1.
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 data5.5.144.0.2403.89
Update Google Chrome to version 44.0.2403.89 or later, and update Qt to version 5.5.1 or later. Organizations should ensure patch management processes cover these applications.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1290 — 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-1290 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