Linux DesktopOperating system · Redhat
CVE-2018-6103
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 · uneditedA stagnant permission prompt in Prompts in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to bypass permission policy 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 stagnant permission prompt vulnerability in Google Chrome versions prior to 66.0.3359.117 allowed remote attackers to bypass the permission policy through a crafted HTML page. The issue involved the permission prompt remaining in a state where it could be exploited, enabling unauthorized access to sensitive browser features.
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
Linux DesktopOperating system
= 6.0
Linux ServerOperating system
= 6.0
Linux WorkstationOperating system
= 6.0
Debian LinuxOperating system
= 8.0= 9.0
ChromeWeb browser
< 66.0.3359.117CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 installed versionOpen Chrome, click the three-dot menu, select Help, then About Google Chrome. The version number is displayed on that page.Affected if The displayed version is less than 66.0.3359.117
-
Check Chrome version via command line (Linux)Run 'google-chrome --version' or 'chromium-browser --version' in terminal to retrieve the installed version number.Affected if The returned version is earlier than 66.0.3359.117
-
Verify Chrome is enabled with permission-dependent featuresEnsure the browser has permissions granted for features like geolocation, microphone, camera, or notifications through the site settings. The vulnerability exploits stagnant permission prompts.Affected if Any site permissions are granted and the browser version is vulnerable
-
Check Red Hat Linux Desktop/Server/Workstation 6.0 browserOn affected Red Hat systems, verify the browser package version using 'rpm -qa | grep chrome' or check installed browser version through the system package manager.Affected if Running Red Hat Linux 6.0 with Chrome version below 66.0.3359.117
-
Check Debian Linux 8.0/9.0 browserOn affected Debian systems, verify browser version using 'dpkg -l | grep chrome' or 'apt list --installed | grep chromium'.Affected if Running Debian 8.0 or 9.0 with Chrome/Chromium version below 66.0.3359.117
A user is affected if their installed Google Chrome or Chromium browser version is lower than 66.0.3359.117 on any operating system, including vulnerable Red Hat Linux 6.0 or Debian Linux 8.0/9.0 configurations.
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 data66.0.3359.117
Update Google Chrome to version 66.0.3359.117 or later to patch the vulnerability. Organizations should ensure automatic updates are enabled or deploy the patched version across all affected endpoints.
Fix this in Linux Desktop
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-6103 — 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-6103 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