Notification restriction bypass via crafted HTML
Published Jun 3, 2020 · Updated Aug 4, 2024
Insufficient policy enforcement in Google Chrome before 74.0.3729.108 allows remote attackers to bypass notification restrictions via crafted HTML. Google identifies the notifications component, but the restricted Chromium issue leaves the faulty code locus and operation undisclosed. A user must open the attacker-controlled page; the documented consequence is limited to bypassing notification restrictions.
Summary
What happened
Insufficient policy enforcement in Google Chrome before 74.0.3729.108 allows remote attackers to bypass notification restrictions via crafted HTML. Google identifies the notifications component, but the restricted Chromium issue leaves the faulty code locus and operation undisclosed. A user must open the attacker-controlled page; the documented consequence is limited to bypassing notification restrictions.
The record
- CVE
- CVE-2020-6504
- Published
- Jun 3, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-276
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 3, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <74.0.3729.108
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo