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.

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.

The remote AlmaLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2020:4442 advisory.

  - An exploitable use after free vulnerability exists in the window function functionality of Sqlite3 3.26.0.
    A specially crafted SQL command can cause a use after free vulnerability, potentially resulting in remote     code execution. An attacker can send a malicious SQL command to trigger this vulnerability.
    (CVE-2019-5018)

  - In SQLite through 3.29.0, whereLoopAddBtreeIndex in sqlite3.c can crash a browser or other application     because of missing validation of a sqlite_stat1 sz field, aka a severe division by zero in the query     planner. (CVE-2019-16168)

  - selectExpander in select.c in SQLite 3.30.1 proceeds with WITH stack unwinding even after a parsing error.
    (CVE-2019-20218)

  - 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)

  - In SQLite 3.31.1, isAuxiliaryVtabOperator allows attackers to trigger a NULL pointer dereference and     segmentation fault because of generated column optimizations. (CVE-2020-9327)

  - ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet     feature. (CVE-2020-13630)

  - SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables, related     to alter.c and build.c. (CVE-2020-13631)

  - ext/fts3/fts3_snippet.c in SQLite before 3.32.0 has a NULL pointer dereference via a crafted matchinfo()     query. (CVE-2020-13632)

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.

  - 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)

  - 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)

  - 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)

  - 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)

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 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.

  - 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)

  - 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)

  - 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)

  - 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)

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

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.

The version of Tencent Linux installed on the remote TencentOS Server 3 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2022:0111 advisory.

    Package updates are available for TencentOS Server 3 that fix the following vulnerabilities:

    CVE-2019-13734:
    Out of bounds write in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to     potentially exploit heap corruption via a crafted HTML page.

    CVE-2019-13752:
    Out of bounds read in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to obtain     potentially sensitive information from process memory via a crafted HTML page.

    CVE-2019-13753:
    Out of bounds read in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to obtain     potentially sensitive information from process memory via a crafted HTML page.

    CVE-2019-16168:
    In SQLite through 3.29.0, whereLoopAddBtreeIndex in sqlite3.c can crash a browser or other application     because of missing validation of a sqlite_stat1 sz field, aka a severe division by zero in the query     planner.

    CVE-2019-19923:
    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-19924:
    SQLite 3.30.1 mishandles certain parser-tree rewriting, related to expr.c, vdbeaux.c, and window.c. This     is caused by incorrect sqlite3WindowRewrite() error handling.

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

    CVE-2019-19959:
    ext/misc/zipfile.c in SQLite 3.30.1 mishandles certain uses of INSERT INTO in situations involving     embedded '\0' characters in filenames, leading to a memory-management error that can be detected by (for     example) valgrind.

    CVE-2019-20218:
    selectExpander in select.c in SQLite 3.30.1 proceeds with WITH stack unwinding even after a parsing error.

    CVE-2019-5018:
    An exploitable use after free vulnerability exists in the window function functionality of Sqlite3 3.26.0.
    A specially crafted SQL command can cause a use after free vulnerability, potentially resulting in remote     code execution. An attacker can send a malicious SQL command to trigger this vulnerability.

    CVE-2019-8457:
    SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode()     function when handling invalid rtree tables.

    CVE-2020-13434:
    SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.

    CVE-2020-13630:
    ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet     feature.

    CVE-2020-13631:
    SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables, related     to alter.c and build.c.

    CVE-2020-13632:
    ext/fts3/fts3_snippet.c in SQLite before 3.32.0 has a NULL pointer dereference via a crafted matchinfo()     query.

    CVE-2020-15358:
    In SQLite before 3.32.3, select.c mishandles query-flattener optimization, leading to a multiSelectOrderBy     heap overflow because of misuse of transitive properties for constant propagation.

    CVE-2020-6405:
    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-9327:
    In SQLite 3.31.1, isAuxiliaryVtabOperator allows attackers to trigger a NULL pointer dereference and     segmentation fault because of generated column optimizations.

Tenable has extracted the preceding description block directly from the Tencent 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.

The remote MiracleLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2020-1005:03 advisory.

    * sqlite: Use-after-free in window function leading to remote code execution (CVE-2019-5018)
      * sqlite: Division by zero in whereLoopAddBtreeIndex in sqlite3.c (CVE-2019-16168)
      * sqlite: selectExpander in select.c proceeds with WITH stack unwinding even after a parsing error     (CVE-2019-20218)
      * sqlite: Out-of-bounds read in SELECT with ON/USING clause (CVE-2020-6405)
      * sqlite: NULL pointer dereference and segmentation fault because of generated column optimizations     (CVE-2020-9327)
      * sqlite: Use-after-free in fts3EvalNextRow in ext/fts3/fts3.c (CVE-2020-13630)
      * sqlite: Virtual table can be renamed into the name of one of its shadow tables (CVE-2020-13631)
      * sqlite: NULL pointer dereference in ext/fts3/fts3_snippet.c via a crafted matchinfo() query     (CVE-2020-13632)

Tenable has extracted the preceding description block directly from the MiracleLinux security advisory.

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

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.

ID	Name	Product	Family	Published	Updated	Severity
134718	Fedora 31 : chromium (2020-f6271d7afa)	Nessus	Fedora Local Security Checks	3/20/2020	12/6/2022	high
134990	Fedora 30 : chromium (2020-39e0b8bd14)	Nessus	Fedora Local Security Checks	3/30/2020	12/6/2022	high
157634	AlmaLinux 8 : sqlite (ALSA-2020:4442)	Nessus	Alma Linux Local Security Checks	2/9/2022	11/10/2023	high
133464	Google Chrome < 80.0.3987.87 Multiple Vulnerabilities	Nessus	MacOS X Local Security Checks	2/4/2020	11/24/2025	high
133465	Google Chrome < 80.0.3987.87 Multiple Vulnerabilities	Nessus	Windows	2/4/2020	11/24/2025	high
133749	RHEL 6 : chromium-browser (RHSA-2020:0514)	Nessus	Red Hat Local Security Checks	2/18/2020	11/7/2024	high
238854	TencentOS Server 3: sqlite (TSSA-2022:0111)	Nessus	Tencent Local Security Checks	6/16/2025	11/20/2025	critical
294583	MiracleLinux 8 : sqlite-3.26.0-11.el8 (AXSA:2020-1005:03)	Nessus	Miracle Linux Local Security Checks	1/20/2026	1/20/2026	high
208457	CentOS 6 : chromium-browser (RHSA-2020:0514)	Nessus	CentOS Local Security Checks	10/9/2024	10/9/2024	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

critical

high

high