Google Chrome prior to 63.0.3239.84 unknown

18 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-15427Google Chrome prior to 63.0.3239.84 unknownInsufficient policy enforcement in Omnibox in Google Chrome prior to 63.0.3239.84 allowed a socially engineered user to XSS themselves by drMEDIUM 6.10.9 %
CVE-2017-15426Google Chrome prior to 63.0.3239.84 unknownInsufficient policy enforcement in Omnibox in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to perform domain spoofing via IMEDIUM 6.51.2 %
CVE-2017-15425Google Chrome prior to 63.0.3239.84 unknownInsufficient policy enforcement in Omnibox in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to perform domain spoofing via IMEDIUM 6.51.2 %
CVE-2017-15424Google Chrome prior to 63.0.3239.84 unknownInsufficient policy enforcement in Omnibox in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to perform domain spoofing via IMEDIUM 6.51.2 %
CVE-2017-15423Google Chrome prior to 63.0.3239.84 unknownInappropriate implementation in BoringSSL SPAKE2 in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to leak the low-order bitsMEDIUM 5.31.5 %
CVE-2017-15422Google Chrome prior to 63.0.3239.84 unknownInteger overflow in international date handling in International Components for Unicode (ICU) for C/C++ before 60.1, as used in V8 in GoogleMEDIUM 6.52.5 %
CVE-2017-15419Google Chrome prior to 63.0.3239.84 unknownInsufficient policy enforcement in Resource Timing API in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to infer browsing hiMEDIUM 6.51.3 %
CVE-2017-15418Google Chrome prior to 63.0.3239.84 unknownUse of uninitialized memory in Skia in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to obtain potentially sensitive informaMEDIUM 4.31.6 %
CVE-2017-15417Google Chrome prior to 63.0.3239.84 unknownInappropriate implementation in Skia canvas composite operations in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to leak crMEDIUM 5.31.5 %
CVE-2017-15416Google Chrome prior to 63.0.3239.84 unknownHeap buffer overflow in Blob API in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to potentially exploit heap corruption viaMEDIUM 6.51.5 %
CVE-2017-15415Google Chrome prior to 63.0.3239.84 unknownIncorrect serialization in IPC in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to leak the value of a pointer via a craftedMEDIUM 6.51.7 %
CVE-2017-15413Google Chrome prior to 63.0.3239.84 unknownType confusion in WebAssembly in V8 in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to potentially exploit heap corruption HIGH 8.81.7 %
CVE-2017-15412Google Chrome prior to 63.0.3239.84 unknownUse after free in libxml2 before 2.9.5, as used in Google Chrome prior to 63.0.3239.84 and other products, allowed a remote attacker to poteHIGH 8.82.9 %
CVE-2017-15411Google Chrome prior to 63.0.3239.84 unknownUse after free in PDFium in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to potentially exploit heap corruption via a craftHIGH 8.81.6 %
CVE-2017-15410Google Chrome prior to 63.0.3239.84 unknownUse after free in PDFium in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to potentially exploit heap corruption via a craftHIGH 8.81.6 %
CVE-2017-15409Google Chrome prior to 63.0.3239.84 unknownHeap buffer overflow in Skia in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to potentially exploit heap corruption via a cHIGH 8.81.6 %
CVE-2017-15408Google Chrome prior to 63.0.3239.84 unknownHeap buffer overflow in Omnibox in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to potentially exploit heap corruption via HIGH 8.81.5 %
CVE-2017-15407Google Chrome prior to 63.0.3239.84 unknownOut-of-bounds Write in the QUIC networking stack in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to gain code execution viaHIGH 8.82.4 %