Multiple stack-based buffer overflows in the AVCC reassembly implementation in Utils.cpp in libstagefright in MediaMuxer in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, 6.x before 2016-09-01, and 7.0 before 2016-09-01 allow remote attackers to execute arbitrary code via a crafted media file, aka internal bug 29161888.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Android | 4.0 (including) | 4.0 (including) | |
| Android | 4.0.1 (including) | 4.0.1 (including) | |
| Android | 4.0.2 (including) | 4.0.2 (including) | |
| Android | 4.0.3 (including) | 4.0.3 (including) | |
| Android | 4.0.4 (including) | 4.0.4 (including) | |
| Android | 4.1 (including) | 4.1 (including) | |
| Android | 4.1.2 (including) | 4.1.2 (including) | |
| Android | 4.2 (including) | 4.2 (including) | |
| Android | 4.2.1 (including) | 4.2.1 (including) | |
| Android | 4.2.2 (including) | 4.2.2 (including) | |
| Android | 4.3 (including) | 4.3 (including) | |
| Android | 4.3.1 (including) | 4.3.1 (including) | |
| Android | 4.4 (including) | 4.4 (including) | |
| Android | 4.4.1 (including) | 4.4.1 (including) | |
| Android | 4.4.2 (including) | 4.4.2 (including) | |
| Android | 4.4.3 (including) | 4.4.3 (including) | |
| Android | 5.0 (including) | 5.0 (including) | |
| Android | 5.0.1 (including) | 5.0.1 (including) | |
| Android | 5.1 (including) | 5.1 (including) | |
| Android | 5.1.0 (including) | 5.1.0 (including) | |
| Android | 6.0 (including) | 6.0 (including) | |
| Android | 6.0.1 (including) | 6.0.1 (including) | |
| Android | 7.0 (including) | 7.0 (including) | |
| Android | Ubuntu | esm-apps/xenial | * |
| Android | Ubuntu | trusty | * |
| Android | Ubuntu | vivid/stable-phone-overlay | * |
| Android | Ubuntu | xenial | * |
| Android | Ubuntu | yakkety | * |
| Android | Ubuntu | zesty | * |
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: