CVE-2016-5194
published 2019-11-20CVE-2016-5194: Unspecified vulnerabilities in Google Chrome before 54.0.2840.59.
PriorityP338critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.73%
50.5th percentile
Unspecified vulnerabilities in Google Chrome before 54.0.2840.59.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | < 54.0.2840.59 | 54.0.2840.59 | |
| chrome | — | — | |
| irssi | irssi | >= 0 < 0.8.15-5ubuntu3.1 | 0.8.15-5ubuntu3.1 |
| irssi | irssi | >= 0 < 0.8.19-1ubuntu1.3 | 0.8.19-1ubuntu1.3 |
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.010.0CRITICALAV:N/AC:L/Au:N/C:C/I:C/A:C
osv9.8CRITICAL
vendor_redhat9.8CRITICAL
vendor_ubuntu1.8LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
Oxide vulnerabilities
vendor_ubuntu·2016-11-02·CVSS 1.8
CVE-2016-1586 [LOW] Oxide vulnerabilities
Title: Oxide vulnerabilities
Summary: Several security issues were fixed in Oxide.
It was discovered that a long running unload handler could cause an
incognito profile to be reused in some circumstances. If a user were
tricked in to opening a specially crafted website, an attacker could
potentially exploit this to obtain sensitive information. (CVE-2016-1586)
Multiple security vulnerabilities were discovered in Chromium. If a user
were tricked in to opening a specially crafted website, an attacker could
potentially exploit these to conduct cross-site scripting (XSS) attacks,
spoof an application's URL bar, obtain sensitive information, cause a
denial of service via application crash, or execute arbitrary code.
(CVE-2016-5181, CVE-2016-5182, CVE-2016-5185, CVE-2016-5186,
CVE-2016-5187,
Red Hat
chromium-browser: various fixes from internal audits
vendor_redhat·2016-10-12·CVSS 9.8
CVE-2016-5194 [CRITICAL] chromium-browser: various fixes from internal audits
chromium-browser: various fixes from internal audits
Unspecified vulnerabilities in Google Chrome before 54.0.2840.59.
GHSA
GHSA-9599-wjxj-x99m: Unspecified vulnerabilities in Google Chrome before 54
ghsa_unreviewed·2022-05-24
CVE-2016-5194 [HIGH] GHSA-9599-wjxj-x99m: Unspecified vulnerabilities in Google Chrome before 54
Unspecified vulnerabilities in Google Chrome before 54.0.2840.59.
OSV
irssi vulnerabilities
osv·2017-02-01·CVSS 3.3
CVE-2016-7553 irssi vulnerabilities
irssi vulnerabilities
It was discovered that the Irssi buf.pl script set incorrect permissions. A
local attacker could use this issue to retrieve another user's window
contents. (CVE-2016-7553)
Joseph Bisch discovered that Irssi incorrectly handled comparing nicks. A
remote attacker could use this issue to cause Irssi to crash, resulting in
a denial of service, or possibly execute arbitrary code. (CVE-2017-5193)
It was discovered that Irssi incorrectly handled invalid nick messages. A
remote attacker could use this issue to cause Irssi to crash, resulting in
a denial of service, or possibly execute arbitrary code. (CVE-2017-5194)
Joseph Bisch discovered that Irssi incorrectly handled certain incomplete
control codes. A remote attacker could use this issue to cause Irssi to
crash, resul
OSV
oxide-qt vulnerabilities
osv·2016-11-02·CVSS 7.5
CVE-2016-1586 [HIGH] oxide-qt vulnerabilities
oxide-qt vulnerabilities
It was discovered that a long running unload handler could cause an
incognito profile to be reused in some circumstances. If a user were
tricked in to opening a specially crafted website, an attacker could
potentially exploit this to obtain sensitive information. (CVE-2016-1586)
Multiple security vulnerabilities were discovered in Chromium. If a user
were tricked in to opening a specially crafted website, an attacker could
potentially exploit these to conduct cross-site scripting (XSS) attacks,
spoof an application's URL bar, obtain sensitive information, cause a
denial of service via application crash, or execute arbitrary code.
(CVE-2016-5181, CVE-2016-5182, CVE-2016-5185, CVE-2016-5186,
CVE-2016-5187, CVE-2016-5188, CVE-2016-5189, CVE-2016-5192, CVE-2016-5194)
OSV
CVE-2016-5194: Unspecified vulnerabilities in Google Chrome before 54
osv·2016-10-17·CVSS 9.8
CVE-2016-5194 [CRITICAL] CVE-2016-5194: Unspecified vulnerabilities in Google Chrome before 54
Unspecified vulnerabilities in Google Chrome before 54.0.2840.59.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2016-5194 chromium-browser: various fixes from internal audits
bugzilla·2016-10-13·CVSS 9.8
CVE-2016-5194 [CRITICAL] CVE-2016-5194 chromium-browser: various fixes from internal audits
CVE-2016-5194 chromium-browser: various fixes from internal audits
Various fixes from internal audits, fuzzing and other initiatives.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=654782
External References:
https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html
Discussion:
Created chromium tracking bugs for this issue:
Affects: fedora-all [bug 1384368]
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6 Supplementary
Via RHSA-2016:2067 https://rhn.redhat.com/errata/RHSA-2016-2067.html
Bugzilla
CVE-2016-5181 CVE-2016-5182 CVE-2016-5183 CVE-2016-5184 CVE-2016-5185 CVE-2016-5186 CVE-2016-5187 CVE-2016-5188 CVE-2016-5189 CVE-2016-5190 CVE-2016-5191 CVE-2016-5192 CVE-2016-5193 CVE-2016-5194 chro
bugzilla·2016-10-13·CVSS 6.1
CVE-2016-5181 [MEDIUM] CVE-2016-5181 CVE-2016-5182 CVE-2016-5183 CVE-2016-5184 CVE-2016-5185 CVE-2016-5186 CVE-2016-5187 CVE-2016-5188 CVE-2016-5189 CVE-2016-5190 CVE-2016-5191 CVE-2016-5192 CVE-2016-5193 CVE-2016-5194 chro
CVE-2016-5181 CVE-2016-5182 CVE-2016-5183 CVE-2016-5184 CVE-2016-5185 CVE-2016-5186 CVE-2016-5187 CVE-2016-5188 CVE-2016-5189 CVE-2016-5190 CVE-2016-5191 CVE-2016-5192 CVE-2016-5193 CVE-2016-5194 chromium: various flaws [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
2019-11-20
Published