mvt-project / mvt-project/androidqf
Check for vulnerable APEX keys
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 281
- Forks
- 48
- Avg merge
- 1h 28m
- Merged PRs (30d)
- 2
Description
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked rtx-cve-2023-45779/apex-checker project and the Android vendors APEX test-keys article. Determine how androidqf should identify vulnerable APEX keys and where such a finding should be reported; done means the check is integrated and reliably flags affected keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, go
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100