A mobile game stores high scores and achievements in a local SQLite database on Android. The developer argues no encryption is needed since high scores are not sensitive. What is the security concern a reviewer might still raise?
- A.An unencrypted SQLite file keeps its page cache pinned in the ART heap, which leaks memory on API 30 or later; the reviewer should raise the leak, not the confidentiality of the scores
- B.A rooted device user can modify the SQLite database directly to cheat by manipulating scores; if the app performs server-side validation, this is low risk, but if rankings are trusted client-side, game integrity is compromised
- C.A database left unencrypted refuses to open once the handset switches to File-Based Encryption, because the platform expects a wrapped page header; the scores become unreadable after an operating system upgrade