Lack of special casing of Android ashmem in Google Chrome prior to 65.0.3325.146 allowed a remote attacker who had compromised the renderer process to bypass inter-process read only guarantees via a crafted HTML page.
Weakness
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Chrome |
Google |
* |
65.0.3325.146 (excluding) |
| Red Hat Enterprise Linux 6 Supplementary |
RedHat |
chromium-browser-0:65.0.3325.146-2.el6_9 |
* |
| Chromium-browser |
Ubuntu |
artful |
* |
| Chromium-browser |
Ubuntu |
trusty |
* |
| Chromium-browser |
Ubuntu |
upstream |
* |
| Chromium-browser |
Ubuntu |
xenial |
* |
| Oxide-qt |
Ubuntu |
artful |
* |
| Oxide-qt |
Ubuntu |
esm-infra/xenial |
* |
| Oxide-qt |
Ubuntu |
trusty |
* |
| Oxide-qt |
Ubuntu |
xenial |
* |
Potential Mitigations
- Run the code in a “jail” or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
- OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
- This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
- Be careful to avoid CWE-243 and other weaknesses related to jails.
References