In setActualDefaultRingtoneUri of RingtoneManager.java,...
High severity
Unreviewed
Published
Jan 22, 2025
to the GitHub Advisory Database
•
Updated Jan 22, 2025
Description
Published by the National Vulnerability Database
Jan 21, 2025
Published to the GitHub Advisory Database
Jan 22, 2025
Last updated
Jan 22, 2025
In setActualDefaultRingtoneUri of RingtoneManager.java, there is a possible way to bypass content providers read permissions due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
References