Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
gemwalletcom/gem-android
main @ eed4e2e
8
Fixes
0
CVEs
HIGH
Peak severity
57.1%
Coverage
Highlights
Auth Bypass: 6 prior fixes. Scrutinize any change in this area.
Handling: most-fixed (1 issue). Treat as high-risk during review.
5 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Auth Bypass: Authentication callbacks could be reused to bypass passcode controls if the callback state is not cleared immediately after validation, or if the application is resumed from the background without re-triggering the required authentication gate.
Auth Bypass: Unvalidated WalletConnect payloads can lead to critical authorization bypasses if session proposals or requests are accepted despite having missing (null) verification context metadata.
Cryptographic Issues: Deriving keys or signing messages using incorrect elliptic curves (such as CURVE25519 instead of ED25519) can cause invalid cryptographic signatures or weaken security properties on keypairs.