Lucene search

K
chromeHttps://chromereleases.googleblog.comGCSA-8860941468848900819
HistoryOct 10, 2019 - 12:00 a.m.

Stable Channel Update for Desktop

2019-10-1000:00:00
https://chromereleases.googleblog.com
chromereleases.googleblog.com
10

CVSS2

6.8

Attack Vector

NETWORK

Attack Complexity

MEDIUM

Authentication

NONE

Confidentiality Impact

PARTIAL

Integrity Impact

PARTIAL

Availability Impact

PARTIAL

AV:N/AC:M/Au:N/C:P/I:P/A:P

CVSS3

8.8

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

REQUIRED

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

HIGH

Availability Impact

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

0.002

Percentile

59.7%

The Stable channel has been updated to 77.0.3865.120 for Windows, Mac, and Linux. This will roll out over the coming days/weeks. A list of all changes is available in the log.

Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven't yet fixed.

This update includes 8 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.

[$20500][1005753] High CVE-2019-13693: Use-after-free in IndexedDB.

Reported by Guang Gong of Alpha Team, Qihoo 360 on 2019-09-19

[$TBD][1005251] High CVE-2019-13694: Use-after-free in WebRTC.

Reported by banananapenguin on 2019-09-18

[$15000][1004730] High CVE-2019-13695: Use-after-free in audio.

Reported by Man Yue Mo of Semmle Security Research Team on 2019-09-17

[$7500][1000635] High CVE-2019-13696: Use-after-free in V8.

Reported by Guang Gong of Alpha Team, Qihoo 360 on 2019-09-04

[$2000][990849] High CVE-2019-13697: Cross-origin size leak.

Reported by Luan Herrera @lbherrera_ on 2019-08-05

We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the Stable channel.

As usual, our ongoing internal security work was responsible for a wide range of fixes:

  • [1011875] Various fixes from internal audits, fuzzing and other initiatives

Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.

Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Lakshmana Pamarthy

Google Chrome

Affected configurations

Vulners
Node
googlechromeRange<77.0.3865.120
CPENameOperatorVersion
google chromelt77.0.3865.120

CVSS2

6.8

Attack Vector

NETWORK

Attack Complexity

MEDIUM

Authentication

NONE

Confidentiality Impact

PARTIAL

Integrity Impact

PARTIAL

Availability Impact

PARTIAL

AV:N/AC:M/Au:N/C:P/I:P/A:P

CVSS3

8.8

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

REQUIRED

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

HIGH

Availability Impact

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

0.002

Percentile

59.7%