Google Chrome prior to 62.0.3202.62

20 published vulnerabilities name this product.

As the CNAs write it in their CVE records (vendor and product); the versions are theirs.

CVEVulnerable versionsTitleSeverityPublishedEPSSExploitation
CVE-2017-5133Google Chrome prior to 62.0.3202.62Off-by-one read/write on the heap in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to corrupt memory and possibly lHIGH 8.82.0 %
CVE-2017-5132Google Chrome prior to 62.0.3202.62Inappropriate implementation in V8 in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit heap corruption vHIGH 8.81.6 %
CVE-2017-5131Google Chrome prior to 62.0.3202.62An integer overflow in Skia in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit heap corruption via a crHIGH 8.81.4 %
CVE-2017-5130Google Chrome prior to 62.0.3202.62An integer overflow in xmlmemory.c in libxml2 before 2.9.5, as used in Google Chrome prior to 62.0.3202.62 and other products, allowed a remHIGH 8.82.7 %
CVE-2017-5129Google Chrome prior to 62.0.3202.62A use after free in WebAudio in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to perform an out of bounds memory reHIGH 8.81.4 %
CVE-2017-5128Google Chrome prior to 62.0.3202.62Heap buffer overflow in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit heap corruption via a HIGH 8.81.6 %
CVE-2017-5127Google Chrome prior to 62.0.3202.62Use after free in PDFium in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit heap corruption via a craftHIGH 8.81.6 %
CVE-2017-5126Google Chrome prior to 62.0.3202.62A use after free in PDFium in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit heap corruption via a craHIGH 8.81.3 %
CVE-2017-5125Google Chrome prior to 62.0.3202.62Heap buffer overflow in Skia in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit heap corruption via a cHIGH 8.81.7 %
CVE-2017-5124Google Chrome prior to 62.0.3202.62Incorrect application of sandboxing in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to inject arbitrary scripts orMEDIUM 6.15.1 %
CVE-2017-15395Google Chrome prior to 62.0.3202.62A use after free in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit heap corruption via a crafMEDIUM 6.51.3 %
CVE-2017-15394Google Chrome prior to 62.0.3202.62Insufficient Policy Enforcement in Extensions in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to perform domain spoofing inMEDIUM 6.51.8 %
CVE-2017-15393Google Chrome prior to 62.0.3202.62Insufficient Policy Enforcement in Devtools remote debugging in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to obtain acceHIGH 8.81.4 %
CVE-2017-15392Google Chrome prior to 62.0.3202.62Insufficient data validation in V8 in Google Chrome prior to 62.0.3202.62 allowed an attacker who can write to the Windows Registry to potenMEDIUM 4.30.8 %
CVE-2017-15391Google Chrome prior to 62.0.3202.62Insufficient Policy Enforcement in Extensions in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to access Extension pages witMEDIUM 6.51.3 %
CVE-2017-15390Google Chrome prior to 62.0.3202.62Insufficient Policy Enforcement in Omnibox in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to perform domain spoofing via IMEDIUM 6.51.2 %
CVE-2017-15389Google Chrome prior to 62.0.3202.62An insufficient watchdog timer in navigation in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to spoof the contents of the OMEDIUM 6.51.3 %
CVE-2017-15388Google Chrome prior to 62.0.3202.62Iteration through non-finite points in Skia in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to perform an out of bounds memHIGH 8.81.6 %
CVE-2017-15387Google Chrome prior to 62.0.3202.62Insufficient enforcement of Content Security Policy in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to open javascHIGH 8.81.4 %
CVE-2017-15386Google Chrome prior to 62.0.3202.62Incorrect implementation in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to spoof the contents of the Omnibox (URLMEDIUM 6.51.5 %