CVE-2017-15392

CVE-2017-15392 relates to Google Chrome/Chromium on Windows and is caused by an incorrect registry key handling in the PlatformIntegration component prior to 62.0.3202.62. A crafted Windows Registry entry could allow heap corruption, potentially enabling code execution or stability issues as desc...

CVE-2017-15392

Removed by vendor...

CVE-2017-15392: Improper Input Validation

Insufficient data validation in V8 in Google Chrome prior to 62.0.3202.62 allowed an attacker who can write to the Windows Registry to potentially exploit heap corruption via a crafted Windows Registry entry, related to PlatformIntegration...

openSUSE Security Update : chromium (openSUSE-2017-1221)

This update to Chromium 62.0.3202.75 fixes the following security issues : - CVE-2017-5124: UXSS with MHTML - CVE-2017-5125: Heap overflow in Skia - CVE-2017-5126: Use after free in PDFium - CVE-2017-5127: Use after free in PDFium - CVE-2017-5128: Heap overflow in WebGL - CVE-2017-5129: Use after...

CVE-2017-15392

Insufficient data validation in V8 in Google Chrome prior to 62.0.3202.62 allowed an attacker who can write to the Windows Registry to potentially exploit heap corruption via a crafted Windows Registry entry, related to PlatformIntegration...

PT-2017-14047

Name of the Vulnerable Software and Affected Versions Google Chrome versions prior to 62.0.3202.62 Opera versions prior to 62.0.3202.62 Description The issue is related to insufficient data validation in V8, which allowed an attacker who can write to the Windows Registry to potentially exploit he...