CVE-2016-5143
Description
The Developer Tools (aka DevTools) subsystem in Blink, as used in Google Chrome before 52.0.2743.116, mishandles the script-path hostname, remoteBase parameter, and remoteFrontendUrl parameter, which allows remote attackers to bypass intended access restrictions via a crafted URL, a different vulnerability than CVE-2016-5144.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A DevTools URL parameter flaw in Chrome before 52.0.2743.116 allows remote attackers to bypass access restrictions via crafted URLs.
Vulnerability
The Developer Tools (DevTools) subsystem in Blink, used by Google Chrome before version 52.0.2743.116, mishandles the script-path hostname, remoteBase parameter, and remoteFrontendUrl parameter. This flaw, distinct from CVE-2016-5144, allows remote attackers to bypass intended access restrictions through a crafted URL [2]. The vulnerability resides in the DevTools front-end code, specifically in Runtime.js [2].
Exploitation
An attacker requires no authentication or special network position; the vulnerability can be exploited by enticing a victim to visit a maliciously crafted URL (e.g., via a web page or link). The attacker manipulates the remoteFrontendUrl and remoteBase parameters, which are not properly whitelisted, enabling the attacker to load arbitrary script paths and bypass security checks [2]. The fix involves whitelisting these parameters and ensuring the hostname is not normalized improperly [2].
Impact
Successful exploitation allows an attacker to bypass access restrictions, potentially leading to arbitrary code execution or sensitive information disclosure. The vulnerability is rated Critical with a CVSS v3 base score of 9.8, and is described as allowing “remote attackers to bypass intended access restrictions” [1][4]. This could enable the attacker to execute commands in the context of the browser process, compromising confidentiality, integrity, and availability.
Mitigation
The vulnerability is fixed in Chrome version 52.0.2743.116 and later [1]. Red Hat Enterprise Linux 6 users received the fix via RHSA-2016:1580, upgrading Chromium to version 52.0.2743.116 [1]. Gentoo users should upgrade to Chromium version 54.0.2840.59 or later per GLSA 201610-09 [4]. No workaround is available other than applying the update. The vulnerability is not listed on CISA’s Known Exploited Vulnerabilities (KEV) catalog.
AI Insight generated on May 23, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
3- Range: < 52.0.2743.116
- osv-coords2 versionspkg:rpm/opensuse/chromium&distro=openSUSE%20Tumbleweedpkg:rpm/suse/chromium&distro=SUSE%20Package%20Hub%2012
< 55.0.2883.75-3.1+ 1 more
- (no CPE)range: < 55.0.2883.75-3.1
- (no CPE)range: < 52.0.2743.116-92.1
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
11- googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop.htmlnvd
- lists.opensuse.org/opensuse-security-announce/2016-08/msg00005.htmlnvd
- lists.opensuse.org/opensuse-security-announce/2016-08/msg00006.htmlnvd
- rhn.redhat.com/errata/RHSA-2016-1580.htmlnvd
- www.debian.org/security/2016/dsa-3645nvd
- www.securityfocus.com/bid/92276nvd
- www.securitytracker.com/id/1036547nvd
- codereview.chromium.org/2065823004nvd
- crbug.com/619414nvd
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4KMX62M7UNRLWO4FEQ6YIMPMTKXXJV6A/nvd
- security.gentoo.org/glsa/201610-09nvd
News mentions
0No linked articles in our index yet.