We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@0x192
Describe the bug If a user restores an arbitrary backup, the backup file could run arbitrary adb shell commands on the Android device.
adb shell
I originally discovered the vulnerability while refactoring UADNG.
See also Universal-Debloater-Alliance/universal-android-debloater-next-generation#760
Expected behavior The backup file is supposed to declaratively specify the package states
You have a solution? Check the cmds in the backup file, and only run each one if it changes the package state.
In the meantime, users should only restore backups they created. Never apply the ones from other users
The text was updated successfully, but these errors were encountered:
No branches or pull requests
@0x192
Describe the bug
If a user restores an arbitrary backup, the backup file could run arbitrary
adb shell
commands on the Android device.I originally discovered the vulnerability while refactoring UADNG.
See also Universal-Debloater-Alliance/universal-android-debloater-next-generation#760
Expected behavior
The backup file is supposed to declaratively specify the package states
You have a solution?
Check the cmds in the backup file, and only run each one if it changes the package state.
In the meantime, users should only restore backups they created. Never apply the ones from other users
The text was updated successfully, but these errors were encountered: