CVE-2017-15419
UnknownEPSS 1.29%
Last modified
CVE-2017-15419 is a vulnerability of currently unknown severity. Insufficient policy enforcement in Resource Timing API in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to infer browsing history by triggering a leaked cross-origin URL via a crafted HTML page.. EPSS estimates a 1.29% chance of exploitation in the next 30 days.
Description
Insufficient policy enforcement in Resource Timing API in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to infer browsing history by triggering a leaked cross-origin URL via a crafted HTML page.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Redhat | Enterprise Linux Desktop | 6.0 |
| Redhat | Enterprise Linux Server | 6.0 |
| Redhat | Enterprise Linux Workstation | 6.0 |
| Debian | Debian Linux | 9.0 |
| Chrome | < 63.0.3239.84 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-15419?
Insufficient policy enforcement in Resource Timing API in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to infer browsing history by triggering a leaked cross-origin URL via a crafted HTML page.
How severe is CVE-2017-15419?
Severity scoring for CVE-2017-15419 is pending analysis. The EPSS model estimates a 1.29% probability of exploitation in the next 30 days.
How do I fix CVE-2017-15419?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- One Click Account Takeover in GranolaHow a notification link broke out of Electron and led to a one-click account takeover.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-15412Use after free in libxml2 before 2.9.5, as used in Google Ch…
- CVE-2017-15413Type confusion in WebAssembly in V8 in Google Chrome prior t…
- CVE-2017-15415Incorrect serialization in IPC in Google Chrome prior to 63.…
- CVE-2017-15416Heap buffer overflow in Blob API in Google Chrome prior to 6…
- CVE-2017-15417Inappropriate implementation in Skia canvas composite operat…
- CVE-2017-15418Use of uninitialized memory in Skia in Google Chrome prior t…
- CVE-2017-15420Incorrect handling of back navigations in error pages in Nav…
- CVE-2017-15422Integer overflow in international date handling in Internati…
- CVE-2017-15423Inappropriate implementation in BoringSSL SPAKE2 in Google C…
- CVE-2017-15424Insufficient policy enforcement in Omnibox in Google Chrome …
- CVE-2017-15425Insufficient policy enforcement in Omnibox in Google Chrome …
- CVE-2017-15426Insufficient policy enforcement in Omnibox in Google Chrome …
Are you affected by CVE-2017-15419?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
