CVE-2018-6153
UnknownEPSS 1.59%
Last modified
CVE-2018-6153 is a vulnerability of currently unknown severity. A precision error in Skia in Google Chrome prior to 68.0.3440.75 allowed a remote attacker who had compromised the renderer process to perform an out of bounds memory write via a crafted HTML page.. EPSS estimates a 1.59% chance of exploitation in the next 30 days.
Description
A precision error in Skia in Google Chrome prior to 68.0.3440.75 allowed a remote attacker who had compromised the renderer process to perform an out of bounds memory write via a crafted HTML page.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | < 68.0.3440.75 | |
| Debian | Debian Linux | 9.0 |
| Redhat | Enterprise Linux Desktop | 6.0 |
| Redhat | Enterprise Linux Server | 6.0 |
| Redhat | Enterprise Linux Workstation | 6.0 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-6153?
A precision error in Skia in Google Chrome prior to 68.0.3440.75 allowed a remote attacker who had compromised the renderer process to perform an out of bounds memory write via a crafted HTML page.
How severe is CVE-2018-6153?
Severity scoring for CVE-2018-6153 is pending analysis. The EPSS model estimates a 1.59% probability of exploitation in the next 30 days.
How do I fix CVE-2018-6153?
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-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-6150Incorrect handling of CORS in ServiceWorker in Google Chrome…
- 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-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
- CVE-2018-6157Type confusion in WebRTC in Google Chrome prior to 68.0.3440…
- CVE-2018-6158A race condition in Oilpan in Google Chrome prior to 68.0.34…
- CVE-2018-6159Insufficient policy enforcement in ServiceWorker in Google C…
Are you affected by CVE-2018-6153?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST