chromium-browser: incorrect registry key handling in platformintegration
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | Google Chrome prior to 62.0.3202.62 | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 6 Supplementary | |||
| chromium-browser-0:62.0.3202.62-2.el6_9 | cpe:/a:redhat:rhel_extras:6 | RHSA-2017:2997 | 2017-10-20T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-4020-1 | chromium-browser security update |
EUVD |
EUVD-2017-6845 | 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. |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.793% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.