CVE-2018-6150
UnknownEPSS 0.87%
Last modified
CVE-2018-6150 is a vulnerability of currently unknown severity. Incorrect handling of CORS in ServiceWorker in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to leak cross-origin data via a crafted HTML page.. EPSS estimates a 0.87% chance of exploitation in the next 30 days.
Description
Incorrect handling of CORS in ServiceWorker in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | < 66.0.3359.117 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-6150?
Incorrect handling of CORS in ServiceWorker in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
How severe is CVE-2018-6150?
Severity scoring for CVE-2018-6150 is pending analysis. The EPSS model estimates a 0.87% probability of exploitation in the next 30 days.
How do I fix CVE-2018-6150?
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
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- 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 2018
- CVE-2018-6143Insufficient validation in V8 in Google Chrome prior to 67.0…
- CVE-2018-6144Off-by-one error in PDFium in Google Chrome prior to 67.0.33…
- CVE-2018-6145Insufficient data validation in HTML parser in Google Chrome…
- CVE-2018-6147Lack of secure text entry mode in Browser UI in Google Chrom…
- CVE-2018-6148Incorrect implementation in Content Security Policy in Googl…
- CVE-2018-6149Type confusion in JavaScript in Google Chrome prior to 67.0.…
- CVE-2018-6151Bad cast in DevTools in Google Chrome on Win, Linux, Mac, Ch…
- CVE-2018-6152The implementation of the Page.downloadBehavior backend unco…
- CVE-2018-6153A precision error in Skia in Google Chrome prior to 68.0.344…
- CVE-2018-6154Insufficient data validation in WebGL in Google Chrome prior…
- CVE-2018-6155Incorrect handling of frames in the VP8 parser in Google Chr…
- CVE-2018-6156Incorect derivation of a packet length in WebRTC in Google C…8.8
Are you affected by CVE-2018-6150?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST