First published: Sat Mar 12 2016(Updated: )
libvpx in mediaserver in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49H, and 6.0 before 2016-03-01 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted media file, related to libwebm/mkvparser.cpp and other files, aka internal bug 23452792.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
Android | =4.0 | |
Android | =4.0.1 | |
Android | =4.0.2 | |
Android | =4.0.3 | |
Android | =4.0.4 | |
Android | =4.1 | |
Android | =4.1.2 | |
Android | =4.2 | |
Android | =4.2.1 | |
Android | =4.2.2 | |
Android | =4.3 | |
Android | =4.3.1 | |
Android | =4.4 | |
Android | =4.4.1 | |
Android | =4.4.2 | |
Android | =4.4.3 | |
Android | =5.0 | |
Android | =5.0.1 | |
Android | =5.0.2 | |
Android | =5.1 | |
Android | =5.1.0 | |
Android | =5.1.1 | |
Android | =6.0 | |
Android | =6.0.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-1621 has a high severity rating due to its potential for execution of arbitrary code or denial of service.
To fix CVE-2016-1621, update the Android operating system to a version released after March 1, 2016.
Devices affected by CVE-2016-1621 may experience memory corruption leading to crashes or the execution of malicious code.
CVE-2016-1621 affects Android versions 4.x, 5.x, and 6.0 up to March 2016.
While updating the OS is the best solution, avoiding the playback of untrusted media files can temporarily mitigate the risk of CVE-2016-1621.