- Apr 21, 2016
- 3,439
The stable channel has been updated to 74.0.3729.131 for Windows, Mac, and Linux, which will roll out over the coming days/weeks.
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 2 security fixes. security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
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.
The following bugs were fixed in previous Chrome releases, but were mistakenly omitted from the release notes at the time:
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.
A list of all changes is available in the log. Interested in switching release channels? Find out how. 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.
Abdul Syed
Google Chrome
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 2 security fixes. security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
- [$500][952406] High CVE to be assigned: Out-of-bounds access in SQLite. Reported by mlfbrown on 2019-04-12
- [$TBD][948564] Medium CVE-2019-5824: Parameter passing error in media player. Reported by leecraso on 2019-04-02
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.
The following bugs were fixed in previous Chrome releases, but were mistakenly omitted from the release notes at the time:
- [$25,633.70][941624] Out-of-bounds write and use-after-free. Reported by l.dmxcsnsbh on 2019-03-13:
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.
A list of all changes is available in the log. Interested in switching release channels? Find out how. 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.
Abdul Syed
Google Chrome
Last edited by a moderator:
