Strix
26.1K

CVE-2016-3750

UnknownEPSS 0.36%

Last modified

CVE-2016-3750 is a vulnerability of currently unknown severity. libs/binder/Parcel.cpp in the Parcels Framework APIs 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-07-01 does not validate the return value of the dup system call, which allows attackers to bypass an isolation protection mechanism via a crafted application, aka internal bug 28395952.. EPSS estimates a 0.36% chance of exploitation in the next 30 days.

Description

libs/binder/Parcel.cpp in the Parcels Framework APIs 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-07-01 does not validate the return value of the dup system call, which allows attackers to bypass an isolation protection mechanism via a crafted application, aka internal bug 28395952.

Metrics

EPSS Probability
0.36%

27.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
GoogleAndroid4.0
GoogleAndroid4.0.1
GoogleAndroid4.0.2
GoogleAndroid4.0.3
GoogleAndroid4.0.4
GoogleAndroid4.1
GoogleAndroid4.1.2
GoogleAndroid4.2
GoogleAndroid4.2.1
GoogleAndroid4.2.2
GoogleAndroid4.3
GoogleAndroid4.3.1
GoogleAndroid4.4
GoogleAndroid4.4.1
GoogleAndroid4.4.2
GoogleAndroid4.4.3
GoogleAndroid5.0
GoogleAndroid5.0.1
GoogleAndroid5.1
GoogleAndroid5.1.0
GoogleAndroid6.0
GoogleAndroid6.0.1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-3750?
libs/binder/Parcel.cpp in the Parcels Framework APIs 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-07-01 does not validate the return value of the dup system call, which allows attackers to bypass an isolation protection mechanism via a crafted application, aka internal bug 28395952.
How severe is CVE-2016-3750?
Severity scoring for CVE-2016-3750 is pending analysis. The EPSS model estimates a 0.36% probability of exploitation in the next 30 days.
How do I fix CVE-2016-3750?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-3750?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST