CVE-2014-7911

Description

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.0 does not verify that deserialization will result in an object that met the requirements for serialization, which allows attackers to execute arbitrary code via a crafted finalize method for a serialized object in an ArrayMap Parcel within an intent sent to system_service, as demonstrated by the finalize method of android.os.BinderProxy, aka Bug 15874291.

Category

7.2
CVSS
Severity: High
CVSS 2.0 •
EPSS 83.89% Top 5%
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://android.googlesource.com/platform/libcore/+/738c833d38d41f8f76eb7e77ab39add82b1ae1e2
http://seclists.org/fulldisclosure/2014/Nov/51 mailing list

Frequently Asked Questions

What is the severity of CVE-2014-7911?
CVE-2014-7911 has been scored as a high severity vulnerability.
How to fix CVE-2014-7911?
To fix CVE-2014-7911, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2014-7911 being actively exploited in the wild?
It is possible that CVE-2014-7911 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~84% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.