CVE-2016-1671Not scoredCWE-22

CVE-2016-1671: Google Chrome vulnerability

Google · Chrome

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

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

1.5%probability of exploitation in the next 30 days

75th percentile

050100

Higher than 75% of scored CVEs

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

DescriptionCVE.org

Google Chrome before 50.0.2661.102 on Android mishandles / (slash) and \ (backslash) characters, which allows attackers to conduct directory traversal attacks via a file: URL, related to net/base/escape.cc and net/base/filename_util.cc.

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: Path Traversal · File and Path Handling
Vendor: Google
Published: May 2016
Band: Possible (1 to 10%), May 2016

CoverageNo articles yet

No CyberSIXT article names CVE-2016-1671 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.