CVE-2025-10184 OnePlus OxygenOS Telephony provider permissio... #1554
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
What’s vulnerable
CVE-2025-10184 is a high-severity flaw (CWE-89 SQL Injection + CWE-862 Missing Authorization) in OnePlus’s OEM-modified Telephony provider (package:
com.android.providers.telephony) on OxygenOS 12–15. Three extra exported content providers added by OnePlus expose write operations without awritePermissionand contain a blind SQL injection inupdate(), letting any installed app (no Android permissions at all) infer and dump SMS/M...🔧 Technical Details
Abusing exported Android ContentProviders with missing write permissions: If an OEM adds exported providers that specify only
readPermission(e.g.,android.permission.READ_SMS) and omitwritePermission, any app can call implemented write operations (insert/update/delete). This enables unauthorized DB writes and, if combined with SQLi sinks, read-equivalent data theft.Blind SQLi via ContentProvider.update(where) as a Boolean oracle: When
update()forwards the caller-controlled WHERE clause to SQLite without sanitization, useunicode(substr((<SUBQUERY>), i, 1)) BETWEEN lo AND hito infer characters. Treatrows_updated > 0orUNIQUE constraint failederrors as “true”; shrink the range until a single code point is found, iterating over characters/rows to reconstruct secrets (e.g.,SELECT body FROM sms ORDER BY rowid DESC LI...🤖 Agent ActionsNo changes made.
Reason: The techniques from the blog (permission bypass via missing writePermission on exported ContentProviders and blind SQL injection through update()’s WHERE clause, including seeding via insert() and sqlite_master probing) are already thoroughly covered in HackTricks.
Where it’s already documented:
src/mobile-pentesting/android-app-pentesting/drozer-tutorial/exploiting-content-providers.md
Additional supportive coverage:
Given the existing page already encapsulates the attack pattern, methodology, example URIs, ADB workflows, and Boolean inference logic, no update is necessary.
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.
📚 Repository Maintenance
All .md files have been checked for proper formatting (headers, includes, etc.).