CVE-2017-5083: Input Validation
First published: Tue Jun 06 2017(Updated: )
Inappropriate implementation in Blink in Google Chrome prior to 59.0.3071.86 for Mac, Windows, and Linux, and 59.0.3071.92 for Android, allowed a remote attacker to display UI on a non attacker controlled tab via a crafted HTML page.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/Chrome | <59.0.3071.86 | 59.0.3071.86 |
| Google Chrome (Trace Event) | <59.0.3071.86 | |
| Apple iOS and macOS | ||
| Linux Kernel | ||
| Microsoft Windows | ||
| Google Chrome (Trace Event) | <59.0.3071.92 | |
| Android | ||
| Red Hat Enterprise Linux Desktop | =6.0 | |
| Red Hat Enterprise Linux Server | =6.0 | |
| Red Hat Enterprise Linux Workstation | =6.0 |
Remedy
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://www.securityfocus.com/bid/98861
- http://www.securitytracker.com/id/1038622
- https://access.redhat.com/errata/RHSA-2017:1399
- https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html
- https://crbug.com/714849
- https://security.gentoo.org/glsa/201706-20
- https://code.google.com/p/chromium/issues/detail?id=714849
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1459040
- https://bugzilla.redhat.com/show_bug.cgi?id=1459036
Frequently Asked Questions
What is the severity of CVE-2017-5083?
CVE-2017-5083 has a high severity rating due to its potential for UI spoofing, allowing attackers to manipulate the user interface.
How do I fix CVE-2017-5083?
To fix CVE-2017-5083, update Google Chrome to version 59.0.3071.86 or later.
What systems are affected by CVE-2017-5083?
CVE-2017-5083 affects Google Chrome versions prior to 59.0.3071.86 for Mac, Windows, and Linux.
What is UI spoofing in the context of CVE-2017-5083?
UI spoofing, as seen in CVE-2017-5083, allows an attacker to manipulate the visual elements of a webpage to mislead users.
Is there a workaround for CVE-2017-5083 until a fix is applied?
There are no recommended workarounds for CVE-2017-5083; updating to the latest version is the best solution.
- agent/type
- agent/first-publish-date
- agent/references
- agent/remedy
- agent/severity
- agent/weakness
- agent/author
- agent/description
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2017-5083
- agent/software-canonical-lookup
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- package-manager/redhat
- vendor/google
- canonical/google chrome (trace event)
- vendor/apple
- canonical/apple ios and macos
- vendor/linux
- canonical/linux kernel
- vendor/microsoft
- canonical/microsoft windows
- canonical/android
- vendor/redhat
- canonical/red hat enterprise linux desktop
- version/red hat enterprise linux desktop/6.0
- canonical/red hat enterprise linux server
- version/red hat enterprise linux server/6.0
- canonical/red hat enterprise linux workstation
- version/red hat enterprise linux workstation/6.0