CVE-2016-10237
If shared content protection memory were passed as the secure camera memory buffer by the HLOS to a trusted application (TA) in all Android releases from CAF using the Linux kernel, the TA would not detect an issue and it would be treated as secure…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.60%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
If shared content protection memory were passed as the secure camera memory buffer by the HLOS to a trusted application (TA) in all Android releases from CAF using the Linux kernel, the TA would not detect an issue and it would be treated as secure memory.
- CVSS 3.0
- 7.8 HIGHCVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS
- 0.60% probability · 47th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-284
- Affected
- google/android
- Source
- security@android.com
References
- http://www.securityfocus.com/bid/97334Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038201
- https://source.android.com/security/bulletin/2017-04-01Patch, Vendor Advisory
- http://www.securityfocus.com/bid/97334Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038201
- https://source.android.com/security/bulletin/2017-04-01Patch, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.