CVE-2017-51308.8HighCWE-190

CVE-2017-5130: Google Chrome prior to 62.0.3202.62 vulnerability

Google · Google Chrome prior to 62.0.3202.62

Fixed in 2.9.5 · Affected: Google Chrome prior to 62.0.3202.62 before 2.9.5 · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

2.7%probability of exploitation in the next 30 days

86th percentile

050100

Higher than 86% of scored CVEs

8.8HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

An 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 remote attacker to potentially exploit heap corruption via a crafted XML file.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

Google Chrome prior to 62.0.3202.62Google Chrome prior to 62.0.3202.62

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Integer Overflow · Memory Corruption
Vendor: Google
Published: February 2018
Band: Possible (1 to 10%), February 2018

CoverageNo articles yet

No CyberSIXT article names CVE-2017-5130 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.