Menu

Star on GitHub · 3.2k

CVE-2016-5173

7.1 · HIGH

The extensions subsystem in Google Chrome before 53.0.2785.113 does not properly restrict access to Object.prototype, which allows remote attackers to load unintended resources, and consequently tr…

Published Sep 25, 2016CWE-284EPSS 1.02%

Overview

CVE-2016-5173 is a high-severity vulnerability. It was published on September 25, 2016 and has a CVSS 3.0 base score of 7.1 (HIGH).

This vulnerability has a CVSS 3.0 base score of 7.1, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

The extensions subsystem in Google Chrome before 53.0.2785.113 does not properly restrict access to Object.prototype, which allows remote attackers to load unintended resources, and consequently trigger unintended JavaScript function calls and bypass the Same Origin Policy via an indirect interception attack.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2016-5173?

CVE-2016-5173 is a high-severity vulnerability. It was published on September 25, 2016 and has a CVSS 3.0 base score of 7.1 (HIGH).

How severe is CVE-2016-5173?

This vulnerability has a CVSS 3.0 base score of 7.1, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2016-5173?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-5173?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-5173 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2016

View all