dbcve.org
ChromeWeb browser · Google

CVE-2016-5174

MEDIUM · 6.5 CVSS v3.0 Published 2016-09-25
Fix available
A fix is available. Upgrade to after 53.0.2785.101 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
browser/ui/cocoa/browser_window_controller_private.mm in Google Chrome before 53.0.2785.113 does not process fullscreen toggle requests during a fullscreen transition, which allows remote attackers to cause a denial of service (unsuppressed popup) 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 confidence

A denial of service vulnerability exists in Google Chrome's macOS (Cocoa) UI implementation where fullscreen toggle requests are not processed during fullscreen transitions. This causes the popup blocker to fail, allowing unsuppressed popups to appear from crafted websites.

MitigationUpdate Google Chrome to version 53.0.2785.113 or later. Users should ensure auto-updates are enabled or manually upgrade to a patched version.

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
Affected:<= 53.0.2785.101

CVSS 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
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Google Chrome version
    Open Chrome and navigate to chrome://version, or click Chrome menu > About Google Chrome. Record the version number shown (e.g., 53.0.2785.101).
    Affected if Version number is 53.0.2785.101 or lower (any version up to and including 53.0.2785.101).
  2. Confirm operating system is macOS
    This vulnerability affects only the macOS (Cocoa) UI implementation. Verify the browser is running on macOS by checking the system OS (Apple menu > About This Mac).
    Affected if Running on macOS with Chrome version 53.0.2785.101 or lower.
  3. Verify popup blocker is enabled
    Go to Chrome settings > Privacy and Security > Site Settings > Popups and redirects, or check chrome://settings/content/popups. Confirm the default setting is 'Do not allow sites to send popups'.
    Affected if Popup blocker is enabled AND Chrome version is 53.0.2785.101 or lower on macOS.

You are affected if Google Chrome version 53.0.2785.101 or lower is running on macOS with the popup blocker enabled, as the fullscreen toggle flaw will cause popups to be unsuppressed during fullscreen transitions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 53.0.2785.101
Interim mitigation

Update Google Chrome to version 53.0.2785.113 or later. Users should ensure auto-updates are enabled or manually upgrade to a patched version.

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-5174 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-5174 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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