Process lifetime issue in Chrome in Google Chrome on Android prior to 74.0.3729.108 allowed a remote attacker to potentially persist an exploited process via a crafted HTML page.
The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Chrome | * | 74.0.3729.108 (excluding) | |
| Chromium-browser | Ubuntu | bionic | * |
| Chromium-browser | Ubuntu | cosmic | * |
| Chromium-browser | Ubuntu | devel | * |
| Chromium-browser | Ubuntu | disco | * |
| Chromium-browser | Ubuntu | eoan | * |
| Chromium-browser | Ubuntu | trusty | * |
| Chromium-browser | Ubuntu | upstream | * |
| Chromium-browser | Ubuntu | xenial | * |
Resources often have explicit instructions on how to be created, used and destroyed. When code does not follow these instructions, it can lead to unexpected behaviors and potentially exploitable states. Even without explicit instructions, various principles are expected to be adhered to, such as “Do not use an object until after its creation is complete,” or “do not use an object after it has been slated for destruction.”