platform/msm_shared/dev_tree.c in the Qualcomm bootloader in Android before 2016-07-05 on Nexus 5 devices does not check the relationship between tags addresses and aboot addresses, which allows attackers to cause a denial of service (OS outage) via a crafted application, aka Android internal bug 28821448 and Qualcomm internal bug CR681965.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Android | * | 6.0.1 (including) | |
Linux-flo | Ubuntu | esm-apps/xenial | * |
Linux-flo | Ubuntu | trusty | * |
Linux-flo | Ubuntu | vivid/stable-phone-overlay | * |
Linux-flo | Ubuntu | wily | * |
Linux-flo | Ubuntu | xenial | * |
Linux-flo | Ubuntu | yakkety | * |
Linux-goldfish | Ubuntu | esm-apps/xenial | * |
Linux-goldfish | Ubuntu | trusty | * |
Linux-goldfish | Ubuntu | wily | * |
Linux-goldfish | Ubuntu | xenial | * |
Linux-goldfish | Ubuntu | yakkety | * |
Linux-goldfish | Ubuntu | zesty | * |
Linux-grouper | Ubuntu | trusty | * |
Linux-linaro-omap | Ubuntu | precise | * |
Linux-linaro-shared | Ubuntu | precise | * |
Linux-linaro-vexpress | Ubuntu | precise | * |
Linux-lts-quantal | Ubuntu | precise | * |
Linux-lts-quantal | Ubuntu | precise/esm | * |
Linux-lts-raring | Ubuntu | precise | * |
Linux-lts-raring | Ubuntu | precise/esm | * |
Linux-lts-saucy | Ubuntu | precise | * |
Linux-lts-saucy | Ubuntu | precise/esm | * |
Linux-maguro | Ubuntu | trusty | * |
Linux-mako | Ubuntu | esm-apps/xenial | * |
Linux-mako | Ubuntu | trusty | * |
Linux-mako | Ubuntu | vivid/stable-phone-overlay | * |
Linux-mako | Ubuntu | wily | * |
Linux-mako | Ubuntu | xenial | * |
Linux-mako | Ubuntu | yakkety | * |
Linux-manta | Ubuntu | trusty | * |
Linux-manta | Ubuntu | wily | * |
Linux-qcm-msm | Ubuntu | precise | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: