大†Shinegumi†大 Posted September 19, 2024 Posted September 19, 2024 (edited) The Chrome web browser has the most significant market share of them all, with 3.45 billion users, so it’s not surprising that many eyes are on the code looking for security flaws. Google has just released version 129 of Chrome, fixing nine security vulnerabilities, and users are urged to update as soon as possible. Here’s what you need to know. What’s New In Google Chrome ? What's new in Chrome 133 Energy Saver Mode One percent of users now benefit from a feature that freezes tabs in energy saver mode. If a tab consumes significant CPU resources and remains hidden for over five minutes, it gets frozen automatically. Chrome Sync Update Chrome Sync no longer supports versions older than four years. To store and sync browser data linked to a Google account across systems, users must use at least Chrome 89. Android JIT Optimizer Setting The Android version introduces a new setting that allows users to disable JIT optimizers in the V8 JavaScript engine. Disabling JIT can improve the security of potentially dangerous web apps by reducing possible attack vectors. On desktop versions, this setting is available in chrome://settings/security since Chrome 122. URL Parsing Standardization Chrome now follows a standard for parsing non-special URL schemes like "git://example.com/path". WebAssembly Memory64 Support WebAssembly gained the ability to use 64-bit pointers (Memory64), enabling work with linear memory areas larger than 4 GB. Developer Tools Enhancements The web developer tools have received updates, including saving your AI-powered chat history across sessions and a new “What’s new?” panel that summarizes the changes in the latest version. Vulnerability Fixes Finally, in addition to introducing new features and fixing bugs, Chrome 133 fixed twelve vulnerabilities. Automated testing tools such as AddressSanitizer, MemorySanitizer, Control Flow Integrity, LibFuzzer, and AFL helped identify many of these issues. Two issues related to accessing freed memory in the V8 engine and Skia library received high severity ratings. No critical issues allowing sandbox bypass or system-level code execution were found. As part of its vulnerability bounty program, Google awarded two bounties totaling $9,000 for this release ($7,000 and $2,000). The amount of one bounty remains unspecified. Windows 11/10 Silent installation Quote https://www.mediafire.com/file/zis0us5n8s2rjd8/Google+Chrome+133.0.6943.127+AIO+Silent+Install.7z/file https://mir.cr/1APBDAPO Windows 7/8 Silent installation Google Chrome 109.0.5414.168 AIO windows 7 last version Install Silent Quote https://www.mediafire.com/file/y480s6kyzu9k81l/Google+Chrome+109.0.5414.168+AIO+Install+Silent.7z/file https://mir.cr/0GHBFW82 Edited Thursday at 03:26 AM by 大†Shinegumi†大 Quote
大†Shinegumi†大 Posted September 25, 2024 Author Posted September 25, 2024 Google Chrome 129.0.6668.71 Update Quote
大†Shinegumi†大 Posted October 2, 2024 Author Posted October 2, 2024 https://developer.chrome.com/release-notes/129 Quote
大†Shinegumi†大 Posted October 30, 2024 Author Posted October 30, 2024 Google Chrome 130.0.6723.92 update Quote
大†Shinegumi†大 Posted January 8 Author Posted January 8 This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug. Android releases contain the same security fixes as their corresponding Desktop (Windows & Mac: 131.0.6778.264/.265 and Linux: 131.0.6778.264) unless otherwise noted. Quote
大†Shinegumi†大 Posted January 23 Author Posted January 23 The Stable channel has been updated to 132.0.6834.110/111 for Windows, Mac and 132.0.6834.110 for Linux which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log. The extended stable channel has been updated to 132.0.6834.110/111( Windows, Mac) and 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 3 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information. [$11000][386143468] High CVE-2025-0611: Object corruption in V8. Reported by 303f06e3 on 2024-12-26 [$8000][385155406] High CVE-2025-0612: Out of bounds memory access in V8.Reported by Alan Goodman on 2024-12-20 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: [391144311] 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. Daniel Yip Google Chrome Quote
大†Shinegumi†大 Posted Thursday at 03:28 AM Author Posted Thursday at 03:28 AM https://chromium.googlesource.com/chromium/src/+log/133.0.6943.89..133.0.6943.121?pretty=fuller&n=10000 Quote
.thumb.jpg.7d51cc81264da0c3589cc92d7d3aed7b.jpg)
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.