ChromeWeb browser · Google
CVE-2014-1743
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 · uneditedUse-after-free vulnerability in the StyleElement::removedFromDocument function in core/dom/StyleElement.cpp in Blink, as used in Google Chrome before 35.0.1916.114, allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via crafted JavaScript code that triggers tree mutation.
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 use-after-free vulnerability in Blink's StyleElement::removedFromDocument function allows crafted JavaScript to trigger tree mutation, causing the browser to access freed memory. This can crash the browser or potentially enable 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
<= 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.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.
-
Identify the browser type and versionOpen Google Chrome, click the menu icon (three dots), select 'Help', then 'About Google Chrome'. Note the version number displayed.Affected if The browser is Google Chrome version 35.0.1916.0 through 35.0.1916.113 (any version <= 35.0.1916.113)
-
Confirm JavaScript execution is enabledIn Chrome settings, go to Privacy and security > Site settings > JavaScript, or inspect any webpage and check if JavaScript executes normally.Affected if JavaScript is enabled (this is the default and required condition for the exploit to trigger)
-
Verify the rendering engine in useIn the Chrome address bar, type 'chrome://version' and look for the 'Blink' or 'WebKit' identifier in the GPU info, or visit a site that displays browser engine information.Affected if The browser uses Blink rendering engine (standard for Chrome 35.x) - this is the component containing the vulnerable StyleElement::removedFromDocument function
If running Google Chrome version 35.0.1916.113 or earlier with JavaScript enabled, the environment is affected by this use-after-free vulnerability in Blink's StyleElement handling.
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. For custom Blink forks, fix the memory management in StyleElement::removedFromDocument to ensure all references are cleared before the element is freed.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1743 — 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-1743 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