Skip to content
New issue

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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 [BUG] - The fact that BlissOS OFFICIAL build's platform key is public should be documented #50

Open
bk138 opened this issue Mar 19, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@bk138
Copy link

bk138 commented Mar 19, 2024

Description

While doing work for a customer I stumbled upon the fact that the official builds available for download at https://blissos.org are built with a publicly available platform key:

This poses a significant security risk for users of the official builds as any adversary can simply sign their app with the platform key and gain elevated permissions for their app.

While it may not be feasible for you guys to keep secret keys for every build, this should at least be documented in the Download and/or Licensing section at https://blissos.org.

Reproduction steps

1. Download and install BlissOS v15.9 OFFICIAL.
2. Download https://github.com/BlissRoms-x86/platform_build/raw/arcadia-x86/target/product/security/platform.pk8 and https://raw.githubusercontent.com/BlissRoms-x86/platform_build/arcadia-x86/target/product/security/platform.x509.pem
3. `apksigner sign --key platform.pk8 --cert platform.x509.pem malicious.apk`
4. `adb install malicious.apk`
5. Watch it 馃挘

Screenshots

No response

Logs

No response

Category

Other

OS Version

15.x

@bk138 bk138 added the bug Something isn't working label Mar 19, 2024
@hmtheboy154
Copy link
Member

That just default AOSP key

@bk138
Copy link
Author

bk138 commented Mar 19, 2024

That just default AOSP key

Yes. I'm suggesting that this should be documented for downloaders/users of the official images as they're probably not aware of what this means and implies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants