CVE-2017-13312 is a high severity flaw in Android: a parcel read/write mismatch in MediaCas.java (createFromParcel). NVD scores it 7.8. Google fixed it in the May 2018 Android Security Bulletin. Devices at security patch level 2018-05-05 or later are covered, so check the level and update.
What's affected
The weakness is a parcel read/write mismatch in MediaCas.java (createFromParcel), in the MediaCas class. The bulletin entry is typed EoP and its affected versions column reads: 8.0. The NVD record is dated 2024-11-15 and carries the vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Google's bulletin and NVD agree on the rating: High in the bulletin, 7.8 (High) in NVD.
The fix is a platform patch, not something you install per app. Per the May 2018 bulletin, security patch levels of 2018-05-05 or later address all issues in that bulletin. Device makers include the fixes in their own updates, so the date a phone reaches that patch level depends on the manufacturer and carrier.
Weakness class: CWE-276.
How to check if you're exposed
Look at the security patch level, not the Android version number. The patch level is the date string that shows which monthly bulletins a device has absorbed.
On the device, open Settings, then About phone, then Android version, and read the Android security patch level. Exact menus vary by manufacturer.
For managed devices with USB debugging enabled, this reads the same value:
adb shell getprop ro.build.version.security_patch
adb shell getprop ro.build.version.release
A patch level earlier than 2018-05-05 means this bulletin has not been fully applied. A device that no longer receives updates cannot be fixed this way and should be retired from sensitive use.
What to do now
- Find every Android device that touches company data and record its patch level, using your mobile device management tool or the commands above.
- Update devices below 2018-05-05 through the manufacturer or carrier channel.
- For devices that cannot reach that level, restrict access to email, source code and admin tools, or replace them.
- Set a compliance rule that blocks devices more than a set number of months behind on patch level.
- Read the original entry in the May 2018 bulletin for anything specific to your hardware.
Why it matters
Android apps and system services exchange objects as Parcels. If the code that writes an object and the code that reads it disagree about how many bytes or which fields are involved, the reader can end up interpreting attacker influenced bytes as trusted fields. The record describes the outcome as an app starting an activity with system privileges.
The record lists CWE 276, incorrect default permissions, although the description itself points to improper input validation. Both ratings describe the same practical gap: input crossing a process boundary was trusted more than it should have been.
This CVE is not on the CISA Known Exploited Vulnerabilities list, and I found no statement of exploitation in the bulletin. That is not a reason to wait. Old Android issues linger because many devices never receive the monthly updates, and the record was only published to NVD in 2024, years after the bulletin.
Safeguard's free in-browser dependency scan at gold.safeguard.sh/scan covers the libraries your own apps ship, not the device operating system. Use it for the app side, and your device management tool for the patch level side.
Quick check
Which patch level fixes CVE-2017-13312?
Google's May 2018 bulletin says security patch levels of 2018-05-05 or later address its issues. Confirm the exact entry in the bulletin for your device and manufacturer.
Is CVE-2017-13312 exploited in the wild?
It is not listed in CISA's Known Exploited Vulnerabilities catalog, and the bulletin text I read does not say it was exploited. Patch anyway.
Sources
Last reviewed: 19 October 2026.
