Insufficient policy enforcement in CORS in Google Chrome prior to 80.0.3987.87 allowed a local attacker to obtain potentially sensitive information via a crafted HTML page.

The remote CentOS Linux 6 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2020:0514 advisory.

  - In xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable isn't reset under certain     circumstances. If the relevant memory area happened to be freed and reused in a certain way, a bounds     check could fail and memory outside a buffer could be written to, or uninitialized data could be     disclosed. (CVE-2019-18197)

  - sqlite: error mishandling because of incomplete fix of (CVE-2019-19880)

  - flattenSubquery in select.c in SQLite 3.30.1 mishandles certain uses of SELECT DISTINCT involving a LEFT     JOIN in which the right-hand side is a view. This can cause a NULL pointer dereference (or incorrect     results). (CVE-2019-19923)

  - zipfileUpdate in ext/misc/zipfile.c in SQLite 3.30.1 mishandles a NULL pathname during an update of a ZIP     archive. (CVE-2019-19925)

  - multiSelect in select.c in SQLite 3.30.1 mishandles certain errors during parsing, as demonstrated by     errors from sqlite3WindowRewrite() calls. NOTE: this vulnerability exists because of an incomplete fix for     CVE-2019-19880. (CVE-2019-19926)

  - Integer overflow in JavaScript in Google Chrome on ChromeOS and Android prior to 80.0.3987.87 allowed a     remote attacker to potentially exploit heap corruption via a crafted HTML page. (CVE-2020-6381)

  - Type confusion in JavaScript in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to     potentially exploit heap corruption via a crafted HTML page. (CVE-2020-6382)

  - Insufficient policy enforcement in storage in Google Chrome prior to 80.0.3987.87 allowed a remote     attacker to bypass site isolation via a crafted HTML page. (CVE-2020-6385)

  - Out of bounds write in WebRTC in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to     potentially exploit heap corruption via a crafted video stream. (CVE-2020-6387, CVE-2020-6389)

  - Out of bounds access in WebAudio in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to     potentially exploit heap corruption via a crafted HTML page. (CVE-2020-6388)

  - Out of bounds memory access in streams in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to     potentially exploit heap corruption via a crafted HTML page. (CVE-2020-6390)

  - Insufficient validation of untrusted input in Blink in Google Chrome prior to 80.0.3987.87 allowed a local     attacker to bypass content security policy via a crafted HTML page. (CVE-2020-6391)

  - Insufficient policy enforcement in extensions in Google Chrome prior to 80.0.3987.87 allowed an attacker     who convinced a user to install a malicious extension to bypass navigation restrictions via a crafted     Chrome Extension. (CVE-2020-6392)

  - Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker     to leak cross-origin data via a crafted HTML page. (CVE-2020-6393)

  - Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker     to bypass content security policy via a crafted HTML page. (CVE-2020-6394)

  - Out of bounds read in JavaScript in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to     obtain potentially sensitive information from process memory via a crafted HTML page. (CVE-2020-6395)

  - Inappropriate implementation in Skia in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to     spoof the contents of the Omnibox (URL bar) via a crafted HTML page. (CVE-2020-6396)

  - Inappropriate implementation in sharing in Google Chrome prior to 80.0.3987.87 allowed a remote attacker     to spoof security UI via a crafted HTML page. (CVE-2020-6397)

  - Use of uninitialized data in PDFium in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to     potentially exploit heap corruption via a crafted PDF file. (CVE-2020-6398)

  - Insufficient policy enforcement in AppCache in Google Chrome prior to 80.0.3987.87 allowed a remote     attacker to leak cross-origin data via a crafted HTML page. (CVE-2020-6399)

  - Inappropriate implementation in CORS in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to     leak cross-origin data via a crafted HTML page. (CVE-2020-6400)

  - Insufficient validation of untrusted input in Omnibox in Google Chrome prior to 80.0.3987.87 allowed a     remote attacker to perform domain spoofing via IDN homographs via a crafted domain name. (CVE-2020-6401,     CVE-2020-6411, CVE-2020-6412)

  - Insufficient policy enforcement in downloads in Google Chrome on OS X prior to 80.0.3987.87 allowed an     attacker who convinced a user to install a malicious extension to execute arbitrary code via a crafted     Chrome Extension. (CVE-2020-6402)

  - Incorrect implementation in Omnibox in Google Chrome on iOS prior to 80.0.3987.87 allowed a remote     attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page. (CVE-2020-6403)

  - Inappropriate implementation in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to     potentially exploit heap corruption via a crafted HTML page. (CVE-2020-6404)

  - Out of bounds read in SQLite in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to obtain     potentially sensitive information from process memory via a crafted HTML page. (CVE-2020-6405)

  - Use after free in audio in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially     exploit heap corruption via a crafted HTML page. (CVE-2020-6406)

  - Insufficient policy enforcement in CORS in Google Chrome prior to 80.0.3987.87 allowed a local attacker to     obtain potentially sensitive information via a crafted HTML page. (CVE-2020-6408)

  - Inappropriate implementation in Omnibox in Google Chrome prior to 80.0.3987.87 allowed a remote attacker     who convinced the user to enter a URI to bypass navigation restrictions via a crafted domain name.
    (CVE-2020-6409)

  - Insufficient policy enforcement in navigation in Google Chrome prior to 80.0.3987.87 allowed a remote     attacker to confuse the user via a crafted domain name. (CVE-2020-6410)

  - Inappropriate implementation in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to     bypass HTML validators via a crafted HTML page. (CVE-2020-6413)

  - Insufficient policy enforcement in Safe Browsing in Google Chrome prior to 80.0.3987.87 allowed a remote     attacker to bypass navigation restrictions via a crafted HTML page. (CVE-2020-6414)

  - Inappropriate implementation in JavaScript in Google Chrome prior to 80.0.3987.87 allowed a remote     attacker to potentially exploit heap corruption via a crafted HTML page. (CVE-2020-6415)

  - Insufficient data validation in streams in Google Chrome prior to 80.0.3987.87 allowed a remote attacker     to potentially exploit heap corruption via a crafted HTML page. (CVE-2020-6416)

  - Inappropriate implementation in installer in Google Chrome prior to 80.0.3987.87 allowed a local attacker     to execute arbitrary code via a crafted registry entry. (CVE-2020-6417)

  - Inappropriate implementation in AppCache in Google Chrome prior to 80.0.3987.87 allowed a remote attacker     to bypass AppCache security restrictions via a crafted HTML page. (CVE-2020-6499)

  - Inappropriate implementation in interstitials in Google Chrome prior to 80.0.3987.87 allowed a remote     attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page. (CVE-2020-6500)

  - Insufficient policy enforcement in CSP in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to     bypass content security policy via a crafted HTML page. (CVE-2020-6501)

  - Incorrect implementation in permissions in Google Chrome prior to 80.0.3987.87 allowed a remote attacker     to spoof security UI via a crafted HTML page. (CVE-2020-6502)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Microsoft Edge (Chromium) installed on the remote Windows host is prior to 80.0.361.48. It is, therefore, affected by multiple vulnerabilities:

  - An integer overflow condition exists in the JavaScript component of Google Chrome. An unauthenticated,     remote attacker can exploit this, via a crafted HTML page, to potentially exploit heap corruption.
    (CVE-2020-6381)

  - A type confusion error exists in the JavaScript component of Google Chrome. An unauthenticated, remote     attacker can exploit this, via a crafted HTML page, to potentially exploit heap corruption.
    (CVE-2020-6382)

  - A use-after-free vulnerability exists in the speech component of Google Chrome. An unauthenticated, remote     attacker can exploit this, via a crafted HTML page, to potentially exploit heap corruption.
    (CVE-2020-6406)

In addition, Microsoft Edge (Chromium) is also affected by several additional vulnerabilities including additional use-after-free vulnerabilities, out-of-bounds read/write, insufficient input validation, and insufficient policy enforcements.

Update to 80.0.3987.149. Upstream says it fixes '13' security issues, but only lists these CVEs :

  - CVE-2020-6422: Use after free in WebGL

  - CVE-2020-6424: Use after free in media

  - CVE-2020-6425: Insufficient policy enforcement in     extensions. 

  - CVE-2020-6426: Inappropriate implementation in V8

  - CVE-2020-6427: Use after free in audio

  - CVE-2020-6428: Use after free in audio

  - CVE-2020-6429: Use after free in audio.

  - CVE-2019-20503: Out of bounds read in usersctplib.

  - CVE-2020-6449: Use after free in audio

----

Update to 80.0.3987.132. Lots of security fixes here. VAAPI re-enabled by default except on NVIDIA.

List of CVEs fixed (since last update) :

  - CVE-2019-20446

  - CVE-2020-6381 

  - CVE-2020-6382 

  - CVE-2020-6383 

  - CVE-2020-6384

  - CVE-2020-6385 

  - CVE-2020-6386

  - CVE-2020-6387 

  - CVE-2020-6388

  - CVE-2020-6389

  - CVE-2020-6390 

  - CVE-2020-6391

  - CVE-2020-6392 

  - CVE-2020-6393

  - CVE-2020-6394

  - CVE-2020-6395

  - CVE-2020-6396 

  - CVE-2020-6397 

  - CVE-2020-6398

  - CVE-2020-6399 

  - CVE-2020-6400 

  - CVE-2020-6401 

  - CVE-2020-6402 

  - CVE-2020-6403 

  - CVE-2020-6404 

  - CVE-2020-6405 

  - CVE-2020-6406 

  - CVE-2020-6407

  - CVE-2020-6408 

  - CVE-2020-6409 

  - CVE-2020-6410 

  - CVE-2020-6411 

  - CVE-2020-6412 

  - CVE-2020-6413 

  - CVE-2020-6414 

  - CVE-2020-6415 

  - CVE-2020-6416 

  - CVE-2020-6417

  - CVE-2020-6418

  - CVE-2020-6420 

----

Update to 79.0.3945.130. Fixes the following security issues :

  - CVE-2020-6378

  - CVE-2020-6379

  - CVE-2020-6380

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Update to 80.0.3987.132. Lots of security fixes here. VAAPI re-enabled by default except on NVIDIA.

List of CVEs fixed (since last update) :

  - CVE-2019-20446

  - CVE-2020-6381 

  - CVE-2020-6382 

  - CVE-2020-6383 

  - CVE-2020-6384

  - CVE-2020-6385 

  - CVE-2020-6386

  - CVE-2020-6387 

  - CVE-2020-6388

  - CVE-2020-6389

  - CVE-2020-6390 

  - CVE-2020-6391

  - CVE-2020-6392 

  - CVE-2020-6393

  - CVE-2020-6394

  - CVE-2020-6395

  - CVE-2020-6396 

  - CVE-2020-6397 

  - CVE-2020-6398

  - CVE-2020-6399 

  - CVE-2020-6400 

  - CVE-2020-6401 

  - CVE-2020-6402 

  - CVE-2020-6403 

  - CVE-2020-6404 

  - CVE-2020-6405 

  - CVE-2020-6406 

  - CVE-2020-6407

  - CVE-2020-6408 

  - CVE-2020-6409 

  - CVE-2020-6410 

  - CVE-2020-6411 

  - CVE-2020-6412 

  - CVE-2020-6413 

  - CVE-2020-6414 

  - CVE-2020-6415 

  - CVE-2020-6416 

  - CVE-2020-6417

  - CVE-2020-6418

  - CVE-2020-6420

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is affected by the vulnerability described in GLSA-202003-08 (Chromium, Google Chrome: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Chromium and Google       Chrome. Please review the referenced CVE identifiers and Google Chrome       Releases for details.
  Impact :

    A remote attacker could execute arbitrary code, escalate privileges,       obtain sensitive information, spoof an URL or cause a Denial of Service       condition.
  Workaround :

    There is no known workaround at this time.

Several vulnerabilities have been discovered in the chromium web browser.

  - CVE-2019-19880     Richard Lorenz discovered an issue in the sqlite     library.

  - CVE-2019-19923     Richard Lorenz discovered an out-of-bounds read issue in     the sqlite library.

  - CVE-2019-19925     Richard Lorenz discovered an issue in the sqlite     library.

  - CVE-2019-19926     Richard Lorenz discovered an implementation error in the     sqlite library.

  - CVE-2020-6381     UK's National Cyber Security Centre discovered an     integer overflow issue in the v8 JavaScript library.

  - CVE-2020-6382     Soyeon Park and Wen Xu discovered a type error in the v8     JavaScript library.

  - CVE-2020-6383     Sergei Glazunov discovered a type error in the v8     JavaScript library.

  - CVE-2020-6384     David Manoucheri discovered a use-after-free issue in     WebAudio.

  - CVE-2020-6385     Sergei Glazunov discovered a policy enforcement error.

  - CVE-2020-6386     Zhe Jin discovered a use-after-free issue in speech     processing.

  - CVE-2020-6387     Natalie Silvanovich discovered an out-of-bounds write     error in the WebRTC implementation.

  - CVE-2020-6388     Sergei Glazunov discovered an out-of-bounds read error     in the WebRTC implementation.

  - CVE-2020-6389     Natalie Silvanovich discovered an out-of-bounds write     error in the WebRTC implementation.

  - CVE-2020-6390     Sergei Glazunov discovered an out-of-bounds read error.

  - CVE-2020-6391     Michal Bentkowski discoverd that untrusted input was     insufficiently validated.

  - CVE-2020-6392     The Microsoft Edge Team discovered a policy enforcement     error.

  - CVE-2020-6393     Mark Amery discovered a policy enforcement error.

  - CVE-2020-6394     Phil Freo discovered a policy enforcement error.

  - CVE-2020-6395     Pierre Langlois discovered an out-of-bounds read error     in the v8 JavaScript library.

  - CVE-2020-6396     William Luc Ritchie discovered an error in the skia     library.

  - CVE-2020-6397     Khalil Zhani discovered a user interface error.

  - CVE-2020-6398     pdknsk discovered an uninitialized variable in the     pdfium library.

  - CVE-2020-6399     Luan Herrera discovered a policy enforcement error.

  - CVE-2020-6400     Takashi Yoneuchi discovered an error in Cross-Origin     Resource Sharing.

  - CVE-2020-6401     Tzachy Horesh discovered that user input was     insufficiently validated.

  - CVE-2020-6402     Vladimir Metnew discovered a policy enforcement error.

  - CVE-2020-6403     Khalil Zhani discovered a user interface error.

  - CVE-2020-6404     kanchi discovered an error in Blink/Webkit.

  - CVE-2020-6405     Yongheng Chen and Rui Zhong discovered an out-of-bounds     read issue in the sqlite library.

  - CVE-2020-6406     Sergei Glazunov discovered a use-after-free issue.

  - CVE-2020-6407     Sergei Glazunov discovered an out-of-bounds read error.

  - CVE-2020-6408     Zhong Zhaochen discovered a policy enforcement error in     Cross-Origin Resource Sharing.

  - CVE-2020-6409     Divagar S and Bharathi V discovered an error in the     omnibox implementation.

  - CVE-2020-6410     evil1m0 discovered a policy enforcement error.

  - CVE-2020-6411     Khalil Zhani discovered that user input was     insufficiently validated.

  - CVE-2020-6412     Zihan Zheng discovered that user input was     insufficiently validated.

  - CVE-2020-6413     Michal Bentkowski discovered an error in Blink/Webkit.

  - CVE-2020-6414     Lijo A.T discovered a policy safe browsing policy     enforcement error.

  - CVE-2020-6415     Avihay Cohen discovered an implementation error in the     v8 JavaScript library.

  - CVE-2020-6416     Woojin Oh discovered that untrusted input was     insufficiently validated.

  - CVE-2020-6418     Clement Lecigne discovered a type error in the v8     JavaScript library.

  - CVE-2020-6420     Taras Uzdenov discovered a policy enforcement error.

The remote Redhat Enterprise Linux 6 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2020:0514 advisory.

    Chromium is an open-source web browser, powered by WebKit (Blink).

    This update upgrades Chromium to version 80.0.3987.87.

    Security Fix(es):

    * chromium-browser: Integer overflow in JavaScript (CVE-2020-6381)

    * chromium-browser: Type Confusion in JavaScript (CVE-2020-6382)

    * chromium-browser: Insufficient policy enforcement in storage (CVE-2020-6385)

    * chromium-browser: Out of bounds write in WebRTC (CVE-2020-6387)

    * chromium-browser: Out of bounds memory access in WebAudio (CVE-2020-6388)

    * chromium-browser: Out of bounds write in WebRTC (CVE-2020-6389)

    * chromium-browser: Out of bounds memory access in streams (CVE-2020-6390)

    * libxslt: use after free in xsltCopyText in transform.c could lead to information disclosure     (CVE-2019-18197)

    * sqlite: invalid pointer dereference in exprListAppendList in window.c (CVE-2019-19880)

    * sqlite: mishandling of certain uses of SELECT DISTINCT involving a LEFT JOIN in flattenSubquery in     select.c leads to a NULL pointer dereference (CVE-2019-19923)

    * sqlite: zipfileUpdate in ext/misc/zipfile.c mishandles a NULL pathname during an update of a ZIP archive     (CVE-2019-19925)

    * sqlite: error mishandling because of incomplete fix of CVE-2019-19880 (CVE-2019-19926)

    * chromium-browser: Insufficient validation of untrusted input in Blink (CVE-2020-6391)

    * chromium-browser: Insufficient policy enforcement in extensions (CVE-2020-6392)

    * chromium-browser: Insufficient policy enforcement in Blink (CVE-2020-6393)

    * chromium-browser: Insufficient policy enforcement in Blink (CVE-2020-6394)

    * chromium-browser: Out of bounds read in JavaScript (CVE-2020-6395)

    * chromium-browser: Inappropriate implementation in Skia (CVE-2020-6396)

    * chromium-browser: Incorrect security UI in sharing (CVE-2020-6397)

    * chromium-browser: Uninitialized use in PDFium (CVE-2020-6398)

    * chromium-browser: Insufficient policy enforcement in AppCache (CVE-2020-6399)

    * chromium-browser: Inappropriate implementation in CORS (CVE-2020-6400)

    * chromium-browser: Insufficient validation of untrusted input in Omnibox (CVE-2020-6401)

    * chromium-browser: Insufficient policy enforcement in downloads (CVE-2020-6402)

    * chromium-browser: Incorrect security UI in Omnibox (CVE-2020-6403)

    * chromium-browser: Inappropriate implementation in Blink (CVE-2020-6404)

    * sqlite: Out-of-bounds read in SELECT with ON/USING clause (CVE-2020-6405)

    * chromium-browser: Use after free in audio (CVE-2020-6406)

    * chromium-browser: Insufficient policy enforcement in CORS (CVE-2020-6408)

    * chromium-browser: Inappropriate implementation in Omnibox (CVE-2020-6409)

    * chromium-browser: Insufficient policy enforcement in navigation (CVE-2020-6410)

    * chromium-browser: Insufficient validation of untrusted input in Omnibox (CVE-2020-6411)

    * chromium-browser: Insufficient validation of untrusted input in Omnibox (CVE-2020-6412)

    * chromium-browser: Inappropriate implementation in Blink (CVE-2020-6413)

    * chromium-browser: Insufficient policy enforcement in Safe Browsing (CVE-2020-6414)

    * chromium-browser: Inappropriate implementation in JavaScript (CVE-2020-6415)

    * chromium-browser: Insufficient data validation in streams (CVE-2020-6416)

    * chromium-browser: Inappropriate implementation in installer (CVE-2020-6417)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

This update for chromium fixes the following issues :

Chromium was updated to version 80.0.3987.87 (boo#1162833).

Security issues fixed :

  - CVE-2020-6381: Integer overflow in JavaScript     (boo#1162833).

  - CVE-2020-6382: Type Confusion in JavaScript     (boo#1162833).

  - CVE-2019-18197: Multiple vulnerabilities in XML     (boo#1162833).

  - CVE-2019-19926: Inappropriate implementation in SQLite     (boo#1162833).

  - CVE-2020-6385: Insufficient policy enforcement in     storage (boo#1162833).

  - CVE-2019-19880, CVE-2019-19925: Multiple vulnerabilities     in SQLite (boo#1162833).

  - CVE-2020-6387: Out of bounds write in WebRTC     (boo#1162833).

  - CVE-2020-6388: Out of bounds memory access in WebAudio     (boo#1162833).

  - CVE-2020-6389: Out of bounds write in WebRTC     (boo#1162833).

  - CVE-2020-6390: Out of bounds memory access in streams     (boo#1162833).

  - CVE-2020-6391: Insufficient validation of untrusted     input in Blink (boo#1162833).

  - CVE-2020-6392: Insufficient policy enforcement in     extensions (boo#1162833).

  - CVE-2020-6393: Insufficient policy enforcement in Blink     (boo#1162833).

  - CVE-2020-6394: Insufficient policy enforcement in Blink     (boo#1162833).

  - CVE-2020-6395: Out of bounds read in JavaScript     (boo#1162833).

  - CVE-2020-6396: Inappropriate implementation in Skia     (boo#1162833).

  - CVE-2020-6397: Incorrect security UI in sharing     (boo#1162833).

  - CVE-2020-6398: Uninitialized use in PDFium     (boo#1162833).

  - CVE-2020-6399: Insufficient policy enforcement in     AppCache (boo#1162833).

  - CVE-2020-6400: Inappropriate implementation in CORS     (boo#1162833).

  - CVE-2020-6401: Insufficient validation of untrusted     input in Omnibox (boo#1162833).

  - CVE-2020-6402: Insufficient policy enforcement in     downloads (boo#1162833).

  - CVE-2020-6403: Incorrect security UI in Omnibox     (boo#1162833).

  - CVE-2020-6404: Inappropriate implementation in Blink     (boo#1162833).

  - CVE-2020-6405: Out of bounds read in SQLite     (boo#1162833).

  - CVE-2020-6406: Use after free in audio (boo#1162833).

  - CVE-2019-19923: Out of bounds memory access in SQLite     (boo#1162833).

  - CVE-2020-6408: Insufficient policy enforcement in CORS     (boo#1162833).

  - CVE-2020-6409: Inappropriate implementation in Omnibox     (boo#1162833).

  - CVE-2020-6410: Insufficient policy enforcement in     navigation (boo#1162833).

  - CVE-2020-6411: Insufficient validation of untrusted     input in Omnibox (boo#1162833).

  - CVE-2020-6412: Insufficient validation of untrusted     input in Omnibox (boo#1162833).

  - CVE-2020-6413: Inappropriate implementation in Blink     (boo#1162833).

  - CVE-2020-6414: Insufficient policy enforcement in Safe     Browsing (boo#1162833).

  - CVE-2020-6415: Inappropriate implementation in     JavaScript (boo#1162833).

  - CVE-2020-6416: Insufficient data validation in streams     (boo#1162833).

  - CVE-2020-6417: Inappropriate implementation in installer     (boo#1162833).

The version of Google Chrome installed on the remote Windows host is prior to 80.0.3987.87. It is, therefore, affected by multiple vulnerabilities as referenced in the 2020_02_stable-channel-update-for-desktop advisory. Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of Google Chrome installed on the remote macOS host is prior to 80.0.3987.87. It is, therefore, affected by multiple vulnerabilities as referenced in the 2020_02_stable-channel-update-for-desktop advisory. Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
208457	CentOS 6 : chromium-browser (RHSA-2020:0514)	Nessus	CentOS Local Security Checks	high
138174	Microsoft Edge (Chromium) < 80.0.361.48 Multiple Vulnerabilities	Nessus	Windows	high
134990	Fedora 30 : chromium (2020-39e0b8bd14)	Nessus	Fedora Local Security Checks	high
134718	Fedora 31 : chromium (2020-f6271d7afa)	Nessus	Fedora Local Security Checks	high
134475	GLSA-202003-08 : Chromium, Google Chrome: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high
134433	Debian DSA-4638-1 : chromium - security update	Nessus	Debian Local Security Checks	high
133749	RHEL 6 : chromium-browser (RHSA-2020:0514)	Nessus	Red Hat Local Security Checks	high
133593	openSUSE Security Update : chromium (openSUSE-2020-189)	Nessus	SuSE Local Security Checks	high
133465	Google Chrome < 80.0.3987.87 Multiple Vulnerabilities	Nessus	Windows	high
133464	Google Chrome < 80.0.3987.87 Multiple Vulnerabilities	Nessus	MacOS X Local Security Checks	high

Detections

Analytics

CVE-2020-6408

medium

Tenable Plugins

high

high

high

high

high

high

high

high

high

high