CVE-2016-5165: XSS
First published: Sun Sep 11 2016(Updated: )
Cross-site scripting (XSS) vulnerability in the Developer Tools (aka DevTools) subsystem in Google Chrome before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on Linux allows remote attackers to inject arbitrary web script or HTML via the settings parameter in a chrome-devtools-frontend.appspot.com URL's query string.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome (Trace Event) | <=52.0.2743.116 | |
| SUSE Linux | =42.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://lists.opensuse.org/opensuse-security-announce/2016-09/msg00003.html
- http://lists.opensuse.org/opensuse-security-announce/2016-09/msg00004.html
- http://lists.opensuse.org/opensuse-security-announce/2016-09/msg00008.html
- http://lists.opensuse.org/opensuse-updates/2016-09/msg00073.html
- http://rhn.redhat.com/errata/RHSA-2016-1854.html
- http://www.debian.org/security/2016/dsa-3660
- http://www.securityfocus.com/bid/92717
- http://www.securitytracker.com/id/1036729
- https://codereview.chromium.org/2177983004
- https://crbug.com/618037
- https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html
- https://security.gentoo.org/glsa/201610-09
Frequently Asked Questions
What is the severity of CVE-2016-5165?
CVE-2016-5165 is classified as a medium-severity cross-site scripting (XSS) vulnerability.
How do I fix CVE-2016-5165?
To mitigate CVE-2016-5165, update Google Chrome to the latest version available beyond 53.0.2785.89.
What does CVE-2016-5165 affect?
CVE-2016-5165 affects versions of Google Chrome prior to 53.0.2785.89 on Windows and OS X, and versions before 53.0.2785.92 on Linux.
Can CVE-2016-5165 be exploited remotely?
Yes, CVE-2016-5165 can be exploited remotely by injecting arbitrary web script or HTML through the settings parameter.
Is there a workaround for CVE-2016-5165?
There is no official workaround for CVE-2016-5165; updating the browser is the recommended solution.
- agent/references
- agent/author
- agent/severity
- agent/type
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/weakness
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/google
- canonical/google chrome (trace event)
- version/google chrome (trace event)/52.0.2743.116
- vendor/opensuse
- canonical/suse linux
- version/suse linux/42.1