ChromeWeb browser · Google
CVE-2018-17474
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 in HTMLImportsController in Blink in Google Chrome prior to 70.0.3538.67 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
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 the HTMLImportsController component of Blink (Google Chrome's rendering engine) allows a remote attacker to exploit heap corruption via a crafted malicious HTML page. The vulnerability exists because memory is freed but a pointer still references it, potentially allowing the attacker to manipulate heap memory and achieve 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
< 70.0.3538.67
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0
Debian LinuxOperating system
= 9.0CVSS 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.
-
Determine if Google Chrome or Chromium browser is installedOn Linux, run: rpm -qa | grep -i chromium OR dpkg -l | grep -i chromium. On Windows, check for Chrome installation in Program Files or via registry.Affected if No browser returned means not affected by this CVE.
-
Check the installed Chrome/Chromium versionRun: chromium-browser --version or google-chrome --version. Compare the version number to 70.0.3538.67.Affected if Version is less than 70.0.3538.67 indicates the system is vulnerable.
-
Verify HTML Imports feature is enabledHTML Imports is enabled by default in affected Chrome versions. This is controlled via chrome://flags/#enable-html-imports. Check if the flag is not explicitly disabled.Affected if HTML Imports is enabled (default state) combined with vulnerable version means the exploit can be triggered.
-
Check for related browser packages on RHEL/CentOS systemsRun: rpm -qa | grep -i 'chrome|chromium' to list any installed Chrome-related packages from Red Hat or third-party repos.Affected if Any Chrome/Chromium package version below 70.0.3538.67 indicates exposure.
A user is affected if Google Chrome or Chromium browser version is below 70.0.3538.67 and HTML Imports feature remains in its default enabled state.
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 data70.0.3538.67
Update Google Chrome to version 70.0.3538.67 or later. For enterprise environments without direct browser update capability, implement application control or browser version management through patch management systems.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17474 — 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-2018-17474 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