CVE-2016-2459: Infoleak

Published May 9, 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.

Affected Software

31 affected components
Google Android=4.0
Google Android=4.0.1
Google Android=4.0.2
Google Android=4.0.3
Google Android=4.0.4
Google Android=4.1
Google Android=4.1.1
Google Android=4.1.2
Google Android=4.2
Google Android=4.2.1
Google Android=4.2.2
Google Android=4.3
Google Android=4.3.1
Google Android=4.4
Google Android=4.4.1
Google Android=4.4.2
Google Android=4.4.3
Google Android=5.0
Google Android=5.0.1
Google Android=5.1
Google Android=6.0
Google Android=6.0.1
Google Android One
Google Nexus 5
Google Nexus 5x
Google Nexus 6
Google Nexus 6p
Google Nexus 7 \(2013\)
Google Nexus 9
Google Nexus Player
Google Pixel C

Event History

May 9, 2016
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203