CVE-2016-2459: Infoleak
First published: Mon May 09 2016(Updated: )
mediaserver in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-05-01 does not initialize certain data structures, which allows attackers to obtain sensitive information via a crafted application, related to IGraphicBufferConsumer.cpp and IGraphicBufferProducer.cpp, aka internal bug 27556038.
Credit: security@android.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.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.1 | |
| Android | =6.0 | |
| Android | =6.0.1 | |
| google Android one | ||
| Google Nexus 5 | ||
| Google Nexus 5X | ||
| Google Nexus 6 | ||
| Google Nexus 6P Firmware | ||
| Google Nexus 7 (2013) | ||
| Google Nexus 9 | ||
| Google Nexus Player | ||
| Google Pixel C |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-2459?
CVE-2016-2459 has been classified as a high severity vulnerability due to its potential to expose sensitive information.
How do I fix CVE-2016-2459?
To fix CVE-2016-2459, users should update their Android devices to the latest software version that patches the vulnerability.
What versions of Android are affected by CVE-2016-2459?
CVE-2016-2459 affects Android versions 4.0 through 6.0.1 before the specific security patch date of May 1, 2016.
What types of attacks can exploit CVE-2016-2459?
CVE-2016-2459 can be exploited by crafted applications to gain unauthorized access to sensitive information stored on the affected device.
Is there a workaround for CVE-2016-2459 if I cannot update my device?
No official workaround exists for CVE-2016-2459, and the best course of action is to update to a secure version of Android.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/google
- canonical/android
- version/android/4.0
- version/android/4.0.1
- version/android/4.0.2
- version/android/4.0.3
- version/android/4.0.4
- version/android/4.1
- version/android/4.1.1
- version/android/4.1.2
- version/android/4.2
- version/android/4.2.1
- version/android/4.2.2
- version/android/4.3
- version/android/4.3.1
- version/android/4.4
- version/android/4.4.1
- version/android/4.4.2
- version/android/4.4.3
- version/android/5.0
- version/android/5.0.1
- version/android/5.1
- version/android/6.0
- version/android/6.0.1
- canonical/google android one
- canonical/google nexus 5
- canonical/google nexus 5x
- canonical/google nexus 6
- canonical/google nexus 6p firmware
- canonical/google nexus 7 (2013)
- canonical/google nexus 9
- canonical/google nexus player
- canonical/google pixel c