CVE-2017-5133Not scoredCWE-787

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

Google · Google Chrome prior to 62.0.3202.62

Vendor fix available · Affected: Google Chrome prior to 62.0.3202.62 · Exploitation: possible (1 to 10%)

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

2.0%probability of exploitation in the next 30 days

80th percentile

050100

Higher than 80% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

Off-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 leak information and potentially execute code via a crafted PDF 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: Out-of-bounds Write · Memory Corruption
Vendor: Google
Published: February 2018
Band: Possible (1 to 10%), February 2018

CoverageNo articles yet

No CyberSIXT article names CVE-2017-5133 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.