ChromeWeb browser · Google
CVE-2018-6049
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 · uneditedIncorrect security UI in permissions prompt in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to spoof the origin to which permission is granted 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 security UI vulnerability in Google Chrome's permissions prompt allowed attackers to spoof the origin displayed when requesting permissions (such as camera, microphone, or location). This could trick users into granting sensitive permissions to malicious sites by making it appear the permission was for a trusted origin.
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
< 64.0.3282.119
Debian LinuxOperating system
= 8.0= 9.0
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.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
- 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 installed Google Chrome versionOpen Google Chrome, click the menu (three dots) > Help > About Google Chrome, or navigate to chrome://settings/helpAffected if The version displayed is lower than 64.0.3282.119
-
Check Chrome version via command line (Linux)Run 'google-chrome --version' or 'chromium --version' in terminalAffected if The reported version number is less than 64.0.3282.119
-
Check Debian package versionRun 'dpkg -l | grep chrome' or 'apt-cache policy chromium' on Debian-based systemsAffected if The installed chromium or google-chrome package version is less than 64.0.3282.119-1
-
Check RHEL package versionRun 'rpm -qa | grep -i chrome' on Red Hat systemsAffected if The installed chrome package version is less than 64.0.3282.119
-
Verify Chrome is used for web browsingConfirm Chrome is the primary browser or that Chrome-derived browsers (Chromium, Edge, etc.) are in useAffected if Chrome or a Chromium-based browser is actively used and its version is below 64.0.3282.119
The environment is affected if Google Chrome or a Chromium-based browser version lower than 64.0.3282.119 is installed and actively used, as this version contains the vulnerable permissions prompt UI.
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 data64.0.3282.119
Update Google Chrome to version 64.0.3282.119 or later to receive the security fix.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6049 — 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-6049 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