Meituan Deletes Photos in Android Permission Bug

💡Meituan photo-delete scandal: AI apps' permission pitfalls for devs.
⚡ 30-Second TL;DR
What Changed
Affected Huawei, Xiaomi, OPPO users; deletions continued post-recovery for hours.
Why It Matters
Exposes risks of over-permissive SDKs in AI-integrated apps, eroding user trust. Pushes for scoped permissions like Google's Photo Picker in Chinese apps.
What To Do Next
Implement Android Photo Picker in your AI image app to limit gallery access.
Key Points
- •Affected Huawei, Xiaomi, OPPO users; deletions continued post-recovery for hours.
- •Rooted in broad Android storage permissions pre-Android 10 read-write unity.
- •SDK cache tool misused photo library as cache due to path errors.
- •Speculates AI-driven smart cleanup from Meituan's local photo analysis models.
- •Breaches Personal Information Protection Law on data control rights.
🧠 Deep Insight
AI-generated analysis for this event — not the original article.
🔑 Enhanced Key Takeaways
- •The incident was traced to a specific version of a third-party advertising SDK integrated into the Meituan app, which incorrectly identified the root directory of the user's photo gallery as a temporary cache folder during a routine cleanup operation.
- •Security researchers identified that the vulnerability exploited the 'Scoped Storage' bypass mechanisms that some older apps maintained to ensure compatibility with legacy Android versions, allowing the SDK to bypass modern OS-level file protection.
- •Following the incident, the Cyberspace Administration of China (CAC) launched a targeted audit of Meituan's data handling practices, specifically focusing on the 'minimal necessity' principle for third-party SDKs.
🛠️ Technical Deep Dive
- •The bug originated from a logic error in a file-path resolution function within the SDK, which used a hardcoded path string that failed to account for dynamic storage partitioning on newer Android versions.
- •The SDK utilized the 'File.delete()' method in Java/Kotlin without implementing a recursive check for directory contents, leading to the accidental deletion of non-cache files when the path resolution pointed to the root of the DCIM folder.
- •The incident highlighted a failure in the app's sandboxing architecture, where the SDK was granted broad 'WRITE_EXTERNAL_STORAGE' permissions, which, prior to Android 11's strict Scoped Storage enforcement, allowed unrestricted access to the entire shared storage volume.
🔮 Future ImplicationsAI analysis grounded in cited sources
⏳ Timeline
Weekly AI Recap
Read this week's curated digest of top AI events →
👉Related Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: 虎嗅 ↗
This is a summary, not the original. Read the source, or get the weekly briefing.
Weekly AI briefing
One email a week. Unsubscribe anytime.


